Skip to main content
DeckTalk ships six agent skills. A skill is a folder with a SKILL.md file, written in the Agent Skills open format, that a coding agent loads when a task matches its description. The skills turn the CLI into something an agent can drive on its own, and they carry the rules that a person would otherwise learn from these docs. The skills live inside the Python package, so every installation carries the skills that match its own CLI. decktalk init writes them into a new project, and Install the skills covers the folders they land in.

​
The six skills

​
What the skills will not do on their own

The skills are written so that an agent cannot spend your money or hide a failure.
  • A voiced run stops and asks. decktalk-build reports the sections a voiced run would voice, their characters, the dollars and the host, and then waits for your approval.
  • No skill passes --force, --exit-zero or an --allow- flag, and no skill turns verify off.
  • No skill edits the [voice] table without asking.
  • decktalk-fix reads findings.items[] and fixes the project. On exit code 3 it stops and reports the error to you, because exit code 3 means DeckTalk itself could not run.
No portable field in the skill format stops a model from starting a skill on its own, so these guards live in the skill text and in the CLI rather than in front matter.

​
The other two agent surfaces

A skill is not the only thing to hand an agent.
  • The reference card puts every file, command, rule and exit code on one page. Hand it to an agent that has no skills loaded.
  • llms.txt indexes every page on this site, and llms-full.txt is the whole site as one file. Hand those to an agent that can fetch a URL.
  • The JSON contract is what an agent reads back after every command.
DeckTalk ships no MCP server. The CLI with --json and its exit codes is the machine interface, and the skills teach an agent to use it.