Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions skills/handoff/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
name: handoff
description: Compact the current conversation into a handoff document for another agent to pick up. Use when ending a session, switching context, or preparing work for the next session.
---

# Handoff

Compact the current conversation into a handoff document for another agent to pick up.

## Process

1. Save to the user's OS temporary directory (not the workspace)
2. Include a "suggested skills" section recommending skills for the next agent
3. Reference existing artifacts (PRDs, plans, ADRs, issues, commits) by path or URL — don't duplicate
4. Redact sensitive data: API keys, passwords, PII
5. If the user provides arguments about next-session focus, tailor the document accordingly

## Required Sections

- **Summary**: What was accomplished this session
- **Current State**: Branch, open files, what's working/broken
- **Next Steps**: Prioritized list of what the next agent should do
- **Key Context**: Architecture decisions, constraints, gotchas the next agent needs
- **Suggested Skills**: Which skills the next agent should invoke
- **References**: Paths/URLs to plans, docs, PRs, issues

## Also Save to Prism

If Prism MCP is available, also call `session_save_handoff` with:
- project name
- active branch
- key context
- open TODOs
- last summary
63 changes: 63 additions & 0 deletions skills/write-a-skill/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
name: write-a-skill
description: Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
---

# Writing Skills

## Process

1. **Gather requirements** — ask about: task/domain, use cases, need for scripts, reference materials
2. **Draft the skill** — create SKILL.md (under 100 lines), split to REFERENCE.md if needed
3. **Review with user** — present draft, iterate

## Structure

```
skill-name/
├── SKILL.md # Main instructions (required, <100 lines)
├── REFERENCE.md # Detailed docs (if >100 lines)
├── EXAMPLES.md # Usage examples (if needed)
└── scripts/ # Utility scripts (if deterministic ops needed)
```

## SKILL.md Template

```md
---
name: skill-name
description: Brief capability description. Use when [specific triggers].
---

# Skill Name

## Quick start
[Minimal working example]

## Workflows
[Step-by-step processes]

## Advanced features
[Link to REFERENCE.md if needed]
```

## Description Rules

- Max 1024 chars, third person
- First sentence: what it does
- Second sentence: "Use when [triggers]"

## When to Add Scripts

Add when: operation is deterministic, same code generated repeatedly, errors need handling.

## When to Split Files

Split when: SKILL.md exceeds 100 lines, content has distinct domains, advanced features rarely needed.

## Review Checklist

- [ ] Description includes "Use when..." triggers
- [ ] SKILL.md under 100 lines
- [ ] No time-sensitive info
- [ ] Concrete examples included
Loading