Sontek Skills

Agent skills and subagents, following the Agent Skills open format.

Installation

Claude Code from local clone

# Clone the repository
git clone git@github.com:sontek/sontek-skills.git ~/sontek-skills

Then inside Claude Code, run these slash commands:

/plugin marketplace add ~/sontek-skills
/plugin install sontek-skills@sontek-skills-local

After installation, restart Claude Code. Skills and agents are automatically invoked when relevant to your task.

Quick Test (No Installation)

# Run Claude Code with the plugin directory directly
claude --plugin-dir ~/sontek-skills/plugins/sontek-skills

Updating

Inside Claude Code, run:

/plugin update sontek-skills@sontek-skills-local

Or use /plugin to open the interactive plugin manager.

What's in this plugin

This plugin ships two kinds of capabilities:

• Skills — atomic workflows the main agent loads inline. verb-object naming (create-pr, review-code, write-skill).
• Agents — persona subagents that run in isolated context and compose skills with judgment. role-noun naming (senior-engineer, security-auditor).

See Skills vs agents for the decision guide.

Available Skills

Git workflow

Code review & audit

Implementation

Planning & design

Diagrams

Session management

Tools & integrations

Sales & GTM

Meta

Available Agents

Agents are persona subagents that run autonomously in isolated context. They use the skills above but bring experience and opinion.

See agents/README.md for invocation triggers and when to use each one.

Skills vs agents

Use the write-skill skill to create either one.

Creating new skills

Skills follow the Agent Skills specification. Each skill requires a SKILL.md file with YAML frontmatter.

Skill template

Create a new directory under plugins/sontek-skills/skills/:

plugins/sontek-skills/skills/my-skill/
└── SKILL.md

SKILL.md format:

---
name: my-skill
description: A clear description of what this skill does. Use when [specific triggers]. Include keywords that help the agent identify when this skill is relevant.
---

# My Skill Name

## Quick start

[Minimal working example]

## Workflow

[Step-by-step guidance]

## Examples

Concrete examples showing expected input/output.

Naming conventions

• name: 1-64 characters, lowercase alphanumeric with hyphens only. verb-object for skills (e.g. create-pr), role-noun for agents (e.g. code-simplifier).
• description: Up to 1024 characters, include trigger keywords and "Use when..." clause.
• Keep SKILL.md under ~100 lines; split longer content into references/*.md.

Wrap prose at 80 chars if desired:

npx prettier --write --prose-wrap always --print-width 80 your-file.md

Optional frontmatter fields

---
name: my-skill
description: What this skill does
license: Apache-2.0
model: sonnet
allowed-tools: Read Grep Glob
---

References

• Agent Skills Specification
• getsentry/sentry-skills — upstream we fork from
• mattpocock/agent-skills — source of clarify (formerly grill-me), improve-architecture, plan-refactor
• ryanthedev/code-foundations and systems-design.skill (Code Complete / APOSD / Clean Architecture / Legacy Code) — techniques folded into clarify, debug, code-reviewer, finding-verifier, improve-architecture, plan-refactor, plan-implementation, review-plan
• mitsuhiko/agent-stuff — source of librarian, update-changelog, sentry, uv, frontend-design, and the Mermaid validation tool used by draw-mermaid-diagram / draw-infra-diagram

License

MPL-2.0