Artifacts, skills and prompts
An artifact is a skill or a prompt you store in Deftro. Each has its own page with Overview, History, Issues, Proposals and Compare tabs.
An artifact is anything you keep in Deftro for an AI agent to use. There are two kinds, and both get versions, the Health check, Review and visibility in the same way.
- Skill: a folder with a
SKILL.mdat its root, plus any reference files or scripts it needs. An agent loads it when your task matches the skill'sdescription. - Prompt: text you insert into a chatbot or agent. It is also written as a
SKILL.md, withkind: promptin its frontmatter.
The Artifacts page
Open Artifacts from the sidebar. The page is called My artifacts and lists the skills and prompts in your personal account, newest first, with how many are published and how many are public.
To add one, press Add in the top bar. See Create or upload an artifact.
An artifact's page
Every artifact has its own page. The header shows its address (owner/name), latest version, visibility and a deftro install command. If you can publish to it, New version takes you to the upload screen. The tabs are:
- Overview: the latest published
SKILL.md, the visibility setting, previews (logo, screenshots and a demo link) and similar artifacts. - History: every version, newest first, with its status, release note and Health check score. From here you restore or yank a version. See Versions and publishing.
- Issues: problems people hit with a specific version. See Proposals, issues and discussions.
- Proposals: edits other people suggested. This tab only appears for people who can publish to the artifact.
- Compare: two versions side by side, every file diffed line by line, with the
SKILL.mdfrontmatter shown first. Pick the two versions on the History tab.
The count beside Issues and Proposals is how many are still open.
Checked against the product on .
Create or upload an artifact
Press Add to upload a SKILL.md, write a skill or prompt in the editor, or import from GitHub. Every artifact needs a name and a description.Versions and publishing
Every change is a new numbered version that only moves forward. A published version never changes; you can yank it to stop new installs, or restore an old one.Review new versions
In an organisation, a new version waits in the Review queue until someone else approves it. You can never review your own version.