Consistent execution
Every run starts with the same baseline instructions.
Save instructions once, name them, and invoke with @ - so every run starts with the same standards and guardrails.
Skills encode how your org wants work done - security notes, review bars, naming, and release rituals.
@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
Every run starts with the same baseline instructions.
New teammates inherit the org’s best prompts on day one.
Update a skill once; every future @invoke picks up the change.
Best-fit scenarios
Deploy checks, security bars, and brand voice are common first skills.
Deploy
Release and rollback ritualsSecurity
Secret handling, scanners, scopeBrand
Voice, UI copy rulesReview
PR quality checklistDocs
README and ADR templatesTreat skills like small products your team maintains.
Capture what actually worked in production.
Pick an @handle the whole team can remember.
Refine when edge cases show up in real runs.
Treat skills like internal documentation: scope access to trusted members and rotate when policies change.
Skills are first-class in threads - invoked by name and shared as team defaults.
Assign an owner per skill; stale skills are worse than none.
Track reuse rate, onboarding time, and defect regressions on standardized flows.
Use Prompt Skills within the same Kodus plans and usage model.
For individual usage.
For small teams.
For larger organizations.
Have invite code? Get Access Now