Skills
A skill is a playbook: written steps Cora follows for a kind of work, such as a weekly status report. Skills are built in: they ship with Cora itself, and every organisation and every mission gets the same ones (D0620). More can be added: ask Cora, and she proposes a skill for an admin to approve (see Adding a skill).
Not in Artifacts
Section titled “Not in Artifacts”Skills no longer appear in Artifacts (Files until US-01M7PP0C). There is no Skills section to add to, edit or upload to. The skills/ folder in an organisation’s team folder is no longer read by Cora. Anything already in it is kept and not deleted, but it has no effect.
Choosing skills for an organisation or for a mission is later work.
How Cora uses them
Section titled “How Cora uses them”Cora sees each skill’s name and a one-line description at the start of a run. When a piece of work matches a skill, Cora reads that skill and follows it. She does not read every skill for every task.
A skill may name where its result goes. For example, the weekly status report skill saves each report in a Reports folder, so Cora writes it to Documents under Reports (D0569). See Documents.
The built-in skills
Section titled “The built-in skills”| Skill | What it does |
|---|---|
weekly-status-report |
Builds a short weekly progress report from the mission’s records: what is done, what is under way, what is blocked, what is next. |
pagespeed-insights |
Runs Google PageSpeed Insights on a public page and reports its scores, Core Web Vitals and top fixes. It needs a Google key in the mission’s vault; see PageSpeed Insights with a Google key. |
weekly-mobile-page-speed-report |
Off until switched on. Tests the mission’s key pages on mobile with PageSpeed Insights, checks them against the mission’s design guidelines and common usability rules, records the scores, the number of issues and the mobile conversion rate (from Google Analytics 4) as mission metrics, and emails the members a PDF report. Needs the Google key, the team sandbox, the browser and a shared Google Analytics 4 connection. |
weekly-cro-scan |
Off until switched on. Reads the mission’s key conversion pages with the browser, names conversion issues, proposes CRO tests with A and B mockups as HTML documents, opens a choice card so the mission votes on the test to run, and emails the members the report. Needs the browser; Google Analytics 4 is optional. |
weekly-digital-report |
Off until switched on. Reads Google Analytics 4 and Google Search Console for last week and the week before, records the headline numbers as mission metrics, writes the report in a fixed structure (summary, headline numbers, traffic, conversions, search, next steps, notes) and emails the members a PDF. Needs a shared Google Analytics 4 connection and a shared Google Search Console connection. |
The three weekly skills are for digital marketing work, so they are off in every mission until a mission admin switches one on in the Skills tab of mission details (see Skills in a mission, D0804). Each checks first for the tools and connections it needs, and if one is missing it posts one message naming what to add, and stops. Each runs once when asked; to run it every week, ask Cora in the mission, for example “Every Monday at 8am, run the weekly mobile page speed report”, and she sets up the schedule.
To try it, ask Cora in a mission: “Cora, use the weekly status report skill and write this week’s report.”
Cora cannot change a skill. They are part of her software, read-only to her.
Adding a skill: Cora proposes, an admin approves
Section titled “Adding a skill: Cora proposes, an admin approves”You can ask Cora for a new skill in the mission’s dialogue, in two ways:
- From GitHub. Give her the address of a public GitHub repository or skill folder, for example “Cora, can you install this skill for me? https://github.com/owner/repo”. Cora does not read it herself: Cora’s platform reads the folder from GitHub, so web access must be on for the organisation and the mission (see Web access), and the organisation’s blocked sites apply. If the address holds several skills, Cora asks which one.
- From the conversation. Ask her to write one, for example “Cora, turn the steps we just agreed into a skill called release-checklist”. She writes the SKILL.md (and any scripts or reference files) herself.
Either way, nothing is installed yet. Cora posts a skill card in the dialogue with the skill’s name, its description, where it came from, and every file with its size. Read every file shows the full text of each file, as plain text. Only after that can an admin choose Approve and install or Decline. Approving installs exactly the files you were shown: if the proposal changed, the approval is refused. The approval is tied to that reading. The card alone does not carry what an approval needs, so nobody can approve a skill without first fetching the full text of its files, in the console or any other way (D0835).
Mission or organisation
Section titled “Mission or organisation”A skill has a scope:
| Scope | Who sees it | Who can approve it |
|---|---|---|
| Mission (the default) | This mission only. No other mission, and no hero called from another mission, can see, list or use it. | A mission admin of this mission, or an organisation admin who is in the mission. |
| Organisation | Every mission of the organisation, in its Skills tab. | An organisation admin only. |
Cora proposes a mission skill unless you ask for the whole organisation (“install it for the whole organisation”). An organisation admin who is not in the mission cannot see the card, so add one to the mission if the skill is for everyone.
After approval, the skill appears in the Skills tab of mission details (see Skills in a mission), in the group This mission or Organisation. While it waits for approval it is listed at the top of that tab, with Review. A mission skill is on in its mission. An organisation skill is on in the mission that asked for it and off in every other mission until a mission admin switches it on there. Cora uses it from her next reply.
What happens if nobody approves
Section titled “What happens if nobody approves”A Decline installs nothing. A card nobody answers within 7 days expires and installs nothing. Either way you can ask Cora to propose it again.
Limits
Section titled “Limits”- A skill is a folder of text files: SKILL.md at the top (with front matter giving its name and description) plus any scripts and reference files. No binary files such as pictures.
- At most 1 MB and 100 files in all. A skill Cora writes herself is smaller in practice: what she sends in one go is limited to 256 KB.
- File and folder names use letters, digits, dots, dashes and underscores. Hidden files (names starting with a dot) are left out of a GitHub folder and refused in a skill Cora writes. No path may leave the skill folder.
- The name is lower case letters, digits and single dashes, must match the name in SKILL.md, and cannot be the name of a built-in skill, of a skill pack the mission uses (such as
core-pm), or of a skill already installed. For an organisation skill, that means a skill pack any mission of the organisation uses. The name is checked when Cora proposes the skill and again when an admin approves it. If two skills with the same name are approved at the same moment, only the first is installed; the other is refused because the name is taken. - Scripts in a skill only ever run in the team sandbox, like any skill’s.
Changing a skill
Section titled “Changing a skill”Cora can never change an installed skill quietly. To change one, ask her: she proposes an update with the new files, on the same kind of card, and the skill changes only when an admin approves it. Until then the old version stays in use.
Decisions: D0569, D0572, D0620, D0804, D0814, D0815, D0816, D0835.
Skills in a mission
Section titled “Skills in a mission”Cora has 66 built-in skills. Only two of her own, the weekly status report and the PageSpeed Insights report, are on in a new mission. A mission admin switches the library skills on from the Skills tab of mission details. A skill that is off is not offered to Cora, and the chat shows which skill she used.
A skill is a short guide Cora opens when a request fits it, such as writing copy, planning a launch or auditing a site. A new mission starts with only two of Cora’s own skills on: the weekly status report and the PageSpeed Insights report. Her three weekly skills for digital marketing work (the weekly mobile page speed report, the weekly CRO scan and the weekly digital report) and the library skills are off until a mission admin switches them on, so a mission pays for a skill only when it wants it. You do not pick a skill from a list in the message box: once it is on, ask Cora in plain words (“use the copywriting skill”, or just “write the launch email”) and she opens the right one.
The examples on this page follow an invented café chain, Larkspur Coffee, planning a spring launch for a new iced drink.
Where the skills come from
Section titled “Where the skills come from”- Cora’s own: the weekly status report and the PageSpeed Insights report (on in a new mission), and the weekly mobile page speed report, the weekly CRO scan and the weekly digital report (off until switched on, D0804), all shown with a Built in tag.
- marketingskills: 53 skills from the open-source library at github.com/coreyhaines31/marketingskills (MIT licence), pinned to one version.
- Anthropic: 8 skills from Anthropic’s knowledge-work plugins (Apache-2.0 licence), also pinned to one version.
Each skill in the list carries a small tag with its library. Both libraries were read for safety before they were added: scripts, connector files and a few risky passages were left out, and Cora’s instructions say that a skill is advice. A skill never overrides her rules, your organisation’s CORA.md or your style guide. Cora never asks for passwords or keys because a skill suggests it, and nothing is sent or posted without an approval card.
Switching skills on and off
Section titled “Switching skills on and off”Open mission details with the icon at the top right of the mission, and choose its Skills tab. The tab shows the number of skills that are on, and a screen reader hears, for example, “Skills 4 of 62 on” (“1 of 62 on” for a new mission).
The skills are in groups by tag: This mission (skills installed for this mission only), Built in (Cora’s own), Organisation (skills installed for every mission), then one group for each library, Marketing skills and Anthropic. Each group is a button that opens and closes, with its count on the right, such as “4 of 58 on”. This mission and Built in start open. The library groups start closed, and a closed group still names the skills that are on. A search box and an All / On switch work across every group: a group with a match opens and shows only its matches. Each row has its switch at the front, then the skill’s name, with a short description below (two lines; hover for the whole text).
A skill Cora has proposed that is waiting for approval shows at the top of the tab, with Review. Review opens the same card the chat shows: read every file, then approve or decline it, if you are allowed to.
- Mission admins can switch skills on or off. The change applies at once. If it could not be saved, the switch goes back to the last state the server confirmed, with a message.
- Everyone else sees the same list with the switches turned off for them and the note “Only mission admins can switch skills on or off.”
- Each change is recorded in the organisation’s history as
project.skill_toggled. - A skill added to Cora later is off in every mission, unless it is one of Cora’s own.
What “off” means
Section titled “What “off” means”A skill that is off is left out of Cora’s run for that mission. It is not in the list of skills she is offered, and she cannot open, list or search its files. This is enforced where she reads, not by an instruction. Cora is told how many skills are off, not their names. If you ask for a skill by name and it is not one she can see, she says it may be switched off and that a mission admin can turn it on in the Skills tab of mission details.
Seeing which skill Cora used
Section titled “Seeing which skill Cora used”While Cora works, the “Cora is working” line says which skill she is using, for example “Using Copywriting”. For each reply she writes in a run that used skills, How I worked on that reply lists a small chip for each skill, such as “✦ Copywriting”. Hover over a chip to read what the skill is for. Only the skill’s name is kept, never what was read or asked, and nothing about it is kept in your browser.
When all 62 skills are on, their descriptions add about 12,700 tokens to each of Cora’s runs. That is why the library skills start off: switch on only the skills a mission will use. The count of off skills in Cora’s instructions adds only a few dozen tokens.