site/docs/schema/SKILL.md
An agent skill providing instructions for AI agents.
npx skillsauth add stencila/stencila site/docs/schemaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
An implementation of the Agent Skills Specification.
A skill is a directory containing a SKILL.md file with YAML frontmatter and a Markdown body
that provides instructions for AI agents. Skills support progressive disclosure: metadata
(~100 tokens) is loaded at startup, full instructions on activation, and referenced files
on demand.
The Skill type has these properties:
| Name | Description | Type | Inherited from |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------ |
| id | The identifier for this item. | String | Entity |
| alternateNames | Alternate names (aliases) for the item. | String* | Thing |
| description | A description of the item. | String | Thing |
| identifiers | Any kind of identifier for any kind of Thing. | (PropertyValue | String)* | Thing |
| images | Images of the item. | ImageObject* | Thing |
| name | The name of the skill. | String | - |
| url | The URL of the item. | String | Thing |
| workType | The type of CreativeWork (e.g. article, book, software application). | CreativeWorkType | CreativeWork |
| doi | The work's Digital Object Identifier (https://doi.org/). | String | CreativeWork |
| about | The subject matter of the content. | ThingVariant* | CreativeWork |
| abstract | A short description that summarizes a CreativeWork. | Block* | CreativeWork |
| authors | The authors of the CreativeWork. | Author* | CreativeWork |
| provenance | A summary of the provenance of the content within the work. | ProvenanceCount* | CreativeWork |
| contributors | A secondary contributor to the CreativeWork. | Author* | CreativeWork |
| editors | People who edited the CreativeWork. | Person* | CreativeWork |
| maintainers | The maintainers of the CreativeWork. | (Person | Organization)* | CreativeWork |
| comments | Comments about this creative work. | Comment* | CreativeWork |
| dateCreated | Date/time of creation. | Date | CreativeWork |
| dateReceived | Date/time that work was received. | Date | CreativeWork |
| dateAccepted | Date/time of acceptance. | Date | CreativeWork |
| dateModified | Date/time of most recent modification. | Date | CreativeWork |
| datePublished | Date of first publication. | Date | CreativeWork |
| funders | People or organizations that funded the CreativeWork. | (Person | Organization)* | CreativeWork |
| fundedBy | Grants that funded the CreativeWork; reverse of fundedItems. | (Grant | MonetaryGrant)* | CreativeWork |
| genre | Genre of the creative work, broadcast channel or group. | String* | CreativeWork |
| keywords | Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas. | String* | CreativeWork |
| isPartOf | An item or other CreativeWork that this CreativeWork is a part of. | CreativeWorkVariant | CreativeWork |
| licenses | License documents that applies to this content, typically indicated by URL, but may be a CreativeWork itself. | (CreativeWorkVariant | String)* | CreativeWork |
| parts | Elements of the collection which can be a variety of different elements, such as Articles, Datatables, Tables and more. | CreativeWorkVariant* | CreativeWork |
| publisher | A publisher of the CreativeWork. | Person | Organization | CreativeWork |
| bibliography | A bibliography of references which may be cited in the work. | Bibliography | CreativeWork |
| references | References to other creative works, such as another publication, web page, scholarly article, etc. | Reference* | CreativeWork |
| text | The textual content of this creative work. | Text | CreativeWork |
| title | The title of the creative work. | Inline* | CreativeWork |
| repository | URL of the repository where the un-compiled, human readable source of the work is located. | String | CreativeWork |
| path | The file system path of the source of the work. | String | CreativeWork |
| commit | The commit hash (or similar) of the source of the work. | String | CreativeWork |
| version | The version of the creative work. | String | Number | CreativeWork |
| frontmatter | Frontmatter containing skill metadata. | String | - |
| content | The content of the skill (the Markdown body). | Block* | - |
| compatibility | Environment requirements for the skill. | String | - |
| allowedTools | Pre-approved tools for the skill. | String* | - |
The Skill type is related to these types:
CreativeWorkThe Skill type is represented in:
SkillSkillSkillThis documentation was generated from Skill.yaml by docs_types.rs.
testing
Critically review a Stencila workflow and suggest improvements. Use when asked to review, audit, critique, evaluate, or improve a workflow directory or WORKFLOW.md file. Covers frontmatter validation, DOT pipeline quality, workflow structure, agent selection quality, discovery metadata, ephemeral workflow conventions, workflow composition, and adherence to Stencila workflow patterns.
development
Create a new Stencila workflow. Use when asked to create, write, scaffold, or set up a workflow directory or WORKFLOW.md file. Covers workflow discovery, duplicate-name checks, ephemeral workflows, WORKFLOW.md frontmatter, DOT pipeline authoring, goals, agents, branching, composition, and validation.
development
Critically review an existing or proposed Stencila theme artifact for correctness, token usage, target coverage, cross-target portability, dark-mode handling, maintainability, and approval readiness. Use when asked to review, critique, assess, audit, or validate a theme.css file, theme patch, theme plan, site theme, document theme, plot theme, print or PDF theme, check design tokens, assess DOCX or email behavior, review dark mode support, or validate with stencila themes validate.
development
Create, update, or plan a Stencila theme for documents or published sites. Use when asked to choose a theme direction, write or patch theme.css, recommend semantic or module token families, customize site navigation or branding, tune PDF and print page tokens, align web, Python, and R plots with a Stencila design system, list available builtin tokens with `stencila themes tokens`, or validate a theme file with `stencila themes validate`.