Install
npx skills add tw93/kami -a claude-code codex cursor -g -yWho it is for
This skill fits when you want an agent to write a document or landing page from existing templates and layout rules, then export PDF, PNG, or slides as editable PowerPoint. It triggers from a natural-language request. No slash command is needed. Official install puts a copy in the shared directory ~/.agents/skills. The install command mentions claude-code, codex, and cursor, but the material does not define support as “only these three”. If you only want to lay out by hand, or you do not need PDF, PNG, or PPT export, do not make it the default entry.
It fits people who already know what the page should say and only lack a reusable layout. It does not fit people with no content outline who expect it to pick the topic. The material only shows that it supplies templates and layout rules and can produce those three export results. It does not say it will fetch research or rewrite marketing copy for you.
First try in 3 minutes
Use only this official install command:
npx skills add tw93/kami -a claude-code codex cursor -g -y
Prerequisite: your environment can run npx, and the agent will read ~/.agents/skills. The install location is that one copy in the shared directory. Do not switch to other install commands that were not written as the main path.
After install, make a low-risk request in one natural-language sentence, for example: using Kami's templates and layout rules, list layout points for a one-page explainer, and do not write files yet. Do not use a slash command to trigger it.
Success signal: the agent gives layout notes from the templates and rules, and you typed no slash command. If it is about to generate PDF, PNG, or PPT, have it report the path and format it will write first, and allow export only after you confirm. The material does not describe a default filename or overwrite policy. If you do not see a new copy in the shared directory, stop and check whether this official command succeeded. Do not switch to an install method that is not the main path.
Use cases
Case 1: Generate a PDF or PNG of a document or landing page from a template. First describe the page purpose and the titles and paragraph blocks that must stay, in natural language. Let the agent apply templates and layout rules, confirm the export path, then generate PDF or PNG. Evidence covers these two exports, but does not give a template roster, sizes, or font limits. Beyond that, stop at “can export by the rules”. Export one format at a time; only consider the other after the file appears.
Case 2: Export slides as editable PowerPoint. First have the agent list each page's title and blocks by the layout rules, confirm page count and output path, then export an editable PPT. Evidence says this export is possible, but does not give a page-count cap, master-slide names, or which elements cannot be edited. Do not run exports back-to-back before the path is confirmed. After export, open it in local software and confirm it is still editable. That is the observable result of this path.
Limits
The official main path is only the npx skills add command above. The copy lands in ~/.agents/skills. Triggering is automatic from natural language; no slash command is required. Export evidence stops at PDF, PNG, and editable PowerPoint. No other formats are described. A client roster must not be inferred as exclusive support from the install flags. Before generating files you must confirm the path, because this writes to disk for real. The material also has no failure rollback or overwrite warning. On repeat export, check yourself whether the target file already exists.