Prompt Skills

Turn your best prompts into reusable team skills

Save instructions once, name them, and invoke with @ - so every run starts with the same standards and guardrails.

  • Brand · security · review checklists
  • Shareable across projects
  • Versioned by iteration
skills/@deploy-checklist.md
Draft“Write deploy verification steps”
SaveName @deploy-checklist
@InvokeRuns on any thread
ImproveTeach once, reuse forever
Prompt Skills

From one-off prompts to shared team defaults

Skills encode how your org wants work done - security notes, review bars, naming, and release rituals.

  • Save prompts with a stable @name
  • Share skills across threads and teammates
  • Keep onboarding fast: new members invoke the same defaults
  • Iterate skills as policies evolve
  • Pair with Review, Strategy, and Design for higher rigor
Skill type: Deploy
Category
Audience
Maturity
@deploy-checklist.skill
Preview
// Skill body:
"@deploy-checklist before production cut"
@deploy-checklist
- Verify feature flags default safe
- Confirm migrations backward compatible
- Run smoke on checkout + auth
- Roll forward plan documented

Owner: release captain
Escalation: #incidents
1Draft
2Save
3Share
4@Run
5Refine

What teams get from Prompt Skills

Consistent execution

Every run starts with the same baseline instructions.

RepeatableLess drift

Faster onboarding

New teammates inherit the org’s best prompts on day one.

TeachableShared

Living standards

Update a skill once; every future @invoke picks up the change.

CentralizedLow overhead

Best-fit scenarios

Use Skills wherever repetition kills quality

Deploy checks, security bars, and brand voice are common first skills.

Reusable Shareable Teachable Consistent
How it works

Build Skills in three moves

Treat skills like small products your team maintains.

Write the winning prompt

Capture what actually worked in production.

Name and publish

Pick an @handle the whole team can remember.

Iterate with usage

Refine when edge cases show up in real runs.

FAQ

Prompt Skills FAQ

Can skills include sensitive instructions?

Treat skills like internal documentation: scope access to trusted members and rotate when policies change.

How is this different from snippets?

Skills are first-class in threads - invoked by name and shared as team defaults.

Who owns maintenance?

Assign an owner per skill; stale skills are worse than none.

How do we measure value?

Track reuse rate, onboarding time, and defect regressions on standardized flows.

Pricing

Pricing

Use Prompt Skills within the same Kodus plans and usage model.

Team

For small teams.

$100/mo
  • 70M tokens / month
  • 2,500 iterations / month
  • Full routing + Review + Strategy
  • Bring your own local model
  • Teams (up to 2 members)
  • Priority support
  • Audit log access

Scale

For larger organizations.

$200/mo
  • 300M tokens / month
  • 7,500 iterations / month
  • Unlimited team members
  • All models + custom routing
  • Dedicated support channel
  • Early access to beta features
  • No annual contract
  • Tokens reset monthly
  • Switch plans anytime

Have invite code? Get Access Now