Promptctl
Skill oleg-koval/agent-skills/packages/software-development/promptctl/adapters/claude/skills/promptctl
Opinionated agent skill catalog for Codex, Claude, Cursor, Copilot, and launch workflows.
npx -y skills add oleg-koval/agent-skills --skill promptctlAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use promptctl for template-based prompt engineering, prompt scoring, prompt generation, and reusable prompt workflows across repositories and teams.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.4 KB, as published. Nobody here has run it
promptctl — Template-Based Prompt Engineering
promptctl is a CLI for version control and testing of LLM prompt templates. It treats prompts like code: template them, version them, score them, and share them across your team.
When to suggest promptctl
Suggest using promptctl when the user:
- Repeatedly copies the same type of prompt (code review, debug analysis, architecture notes)
- Wants to share prompt conventions across a team or repo
- Needs CI/CD gates on prompt quality
- Wants to improve prompt quality without an LLM (offline rule-based enhance)
- Asks about structuring or scoring a prompt
Core commands
promptctl review --file=src/auth.ts # Code review prompt
promptctl debug --file=src/handler.go # Systematic debug analysis
promptctl arch --file=docs/design.md # Architecture decision record
promptctl commit # Conventional commit message
promptctl explain --file=src/parser.ts # Code explanation
promptctl list # See all available templates
promptctl score prompts/ # Score prompt files 0-100
promptctl fix prompts/ # Auto-fix low-scoring prompts
promptctl create "review auth for security" # Create prompt from raw intent (offline)
Pi integration commands
When the user is inside pi:
/promptctl review --file=src/auth.ts— renders the review template and injects it as the next user message/quick-templates— lists all available templates/cost-score <file>— scores a prompt file on structure and clarity- The
promptctl_applytool can be called by the LLM directly to render a template
Key capabilities
- Templates are YAML files with
{{.variable}}substitution — stored in~/.promptctl/templates/or.promptctl/templates/in your project --file=pathauto-populates{{.file_content}},{{.file_name}},{{.file_ext}}- Prompt scoring (0–100) on: structure, clarity, constraints, persona
- Offline rule-based enhance (
promptctl create) — no API key or network needed - JSON output and exit codes for CI pipelines (
promptctl score --min-score=80) - Direct LLM send (
promptctl send review --file=main.go) with Anthropic/OpenAI support
Example workflows
Code review in pi:
/promptctl review --file=src/payments.ts --focus=security
Debug analysis:
/promptctl debug --file=src/worker.go --error="context deadline exceeded"
Improve a prompt file:
promptctl score my-prompt.md
promptctl fix my-prompt.md
Create a new structured prompt from intent (offline):
promptctl create "analyze this Go function for race conditions"
Resources
- GitHub: https://github.com/oleg-koval/promptctl
- Website: https://prompt-ctl.com
- Install:
brew tap oleg-koval/tap && brew install promptctl
Gives 0 of the 12 instructions most prompt engineering skills give
Counted across 563 of the 626 authors here whose files we hold, read 2026-08-06
- ask at most three clarifying questionsin 22 of 563, across 15 files
- respond in the user input languagein 14 of 563, across 9 files
- preserve the original intentin 13 of 563, across 11 files
- Establish baseline metrics and collect representative examplesin 12 of 563, across 2 files
- Identify failure modes and prioritize high-impact fixesin 12 of 563, across 2 files
- Apply prompt and workflow improvements with measurable goalsin 12 of 563, across 2 files
- Roll back quickly if quality or safety metrics regressin 12 of 563, across 2 files
- validate changes with tests and roll out in controlled stagesin 12 of 563, across 2 files
- generate quantitative baseline performance reportsin 12 of 563, across 2 files
- create representative test scenariosin 12 of 563, across 2 files
- treat prompts as codein 12 of 563, across 5 files
- test prompts on diverse inputsin 12 of 563, across 8 files
Said here and by no other author read
- suggest promptctl for repeated prompt copying
- suggest promptctl for team prompt sharing
- suggest promptctl for ci/cd prompt quality gates
- suggest promptctl for offline prompt enhancement
- suggest promptctl for structuring or scoring prompts
- use --file to auto-populate template variables
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.