Agent skill
agents
Create mdflow-backed agent files for Script Kit. Use when the user wants to create AI agents, configure agent backends (Claude, Gemini, Codex), or manage agent metadata.
Install this agent skill to your Project
npx add-skill https://github.com/johnlindquist/script-kit-next/tree/main/kit-init/skills/agents
SKILL.md
Agents
Create mdflow-backed agent files for Script Kit.
Where Agents Live
~/.scriptkit/kit/main/agents/*.md
Filename Rules
| Filename | Meaning |
|---|---|
review.claude.md |
Claude backend |
plan.gemini.md |
Gemini backend |
code.codex.md |
Codex backend |
triage.copilot.md |
Copilot backend |
chat.i.gemini.md |
Interactive agent (.i. or _interactive: true) |
generic.md |
Generic agent; use _command when needed |
Script Kit Metadata Keys
Use underscore-prefixed keys so Script Kit metadata does not leak to backend CLI flags.
_sk_name_sk_description_sk_icon_sk_alias_sk_shortcut
mdflow System Keys
_inputs_interactiveor_i_cwd_env_command
Minimal Template
---
_sk_name: "Review PR"
_sk_description: "Review staged changes and call out risks"
_sk_icon: "git-pull-request"
model: sonnet
---
Review the current git diff.
Return:
1. findings ordered by severity
2. concrete fixes
3. tests to add
Interactive Template
---
_sk_name: "Plan Feature"
_sk_description: "Turn a feature request into an implementation plan"
_sk_icon: "map"
_interactive: true
_inputs:
feature_name:
type: text
message: "Feature name?"
risk_tolerance:
type: select
message: "Risk tolerance?"
choices: ["low", "medium", "high"]
model: gemini-2.0-flash
---
Create an implementation plan for {{ feature_name }}.
Risk tolerance: {{ risk_tolerance }}.
Include:
- files to change
- data flow
- tests to add
- rollback plan
Common Mistakes
- Do not put agent files in
scripts/ - Do not use
export const metadata - Do not omit the backend suffix when you want a specific CLI
- Do not use non-underscore
sk_*keys
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
johnlindquist/script-kit-next
Generate Component Documentation
Based on existing docs styles and specific API implementations, and referencing same name stories, generate comprehensive documentation for the new component.
johnlindquist/script-kit-next
Generate Component Story
Generate a comprehensive story for a new component for as example.
johnlindquist/script-kit-next
new-component
How to write a new component of GPUI Component.
johnlindquist/script-kit-next
troubleshooting
Diagnose and fix common Script Kit issues. Use when the user reports bugs, crashes, missing features, or unexpected behavior in Script Kit GPUI.
johnlindquist/script-kit-next
script-authoring
Create and manage TypeScript scripts for Script Kit. Use when the user wants to write a new script, edit an existing script, or understand Script Kit's SDK and metadata system.
johnlindquist/script-kit-next
scriptlets
Create extension bundles (scriptlets) for text expansions, snippets, shell commands, and lightweight helpers in a single markdown file. Use when the user wants quick shortcuts or grouped utilities.
Didn't find tool you were looking for?