open/claude-code-complete-agent
1
0
Fork 0
Code Activity Actions

fix: reference plugin-dev throughout Example 14 and GETTING-STARTED

Browse source 
Skills, agents, and hooks should be created via plugin-dev plugin,
not generic "tell Claude" or manual file writing.

Example 14: /agent-development for agents, /skill-development for
pipeline skills, /hook-development for hooks, /skill-reviewer for
quality checks, /plugin-validator for setup validation. plugin-dev
added as prerequisite.

GETTING-STARTED.md: /skill-development for skill creation,
/skill-reviewer for iteration, /mcp-integration for MCP servers.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-03-26 21:43:15 +01:00
commit 866e8a5f3b
2 changed files with 124 additions and 61 deletions
Download patch file Download diff file Expand all files Collapse all files

40
GETTING-STARTED.md
View file

@ -152,20 +152,27 @@ always-on, but covers most situations.
## Step 4: Create your first personal skill (15 minutes)
Skills transform Claude Code from "general AI assistant" into
"my assistant that knows how I work." You do not write skill
files by hand. You describe what you need and let Claude create
the file with the correct format.
"my assistant that knows how I work." You use the **plugin-dev**
plugin to create them. It handles the file format, YAML
frontmatter, description quality, and file placement.
If you do not have plugin-dev installed:
```
/install plugin-dev
```
### How it works
Tell Claude what you want the skill to do. It creates the file
with proper YAML frontmatter (required for Claude Code to
recognize it as a skill) and markdown body.
Run `/skill-development` and describe what you need. The guided
workflow creates the skill file with proper structure. You never
need to write skill files by hand.
### Example: Weekly status report
```
Create a skill called "weekly-status" that generates my weekly
/skill-development
I need a skill called "weekly-status" that generates my weekly
status report. It should:
1. Read CLAUDE.md for current priorities
2. Check git log for this week's activity
@ -173,21 +180,21 @@ status report. It should:
4. Write a concise report: what was completed, what is in
progress, what is blocked, plan for next week
Format: bullet points, under 300 words, lead with wins.
Save it to .claude/skills/weekly-status.md
```
Claude creates the file. Now you can run `/weekly-status` every
Monday morning. Or text "Run /weekly-status" from your phone.
The plugin creates the file. Now you can run `/weekly-status`
every Monday morning. Or text "Run /weekly-status" from your phone.
### Example: Research and save
```
Create a skill called "deep-research" that researches a given
/skill-development
I need a skill called "deep-research" that researches a given
topic thoroughly. It should search the web, cross-reference
claims across sources, and write a structured summary to
research/[topic-slug]-[date].md with key findings, details,
what could not be verified, and source URLs.
Save it to .claude/skills/deep-research.md
```
### Example: Daily briefing
@ -213,6 +220,10 @@ each section at 3 bullets and total output at 200 words.
Claude updates the skill file. Run it again. Most skills take
2-3 iterations to produce output you are happy with.
After iterating, run `/skill-reviewer` to check quality. It catches
common issues: vague descriptions that will not trigger correctly,
missing edge cases, and structural problems.
### When to create a skill
A skill is worth creating when you:
@ -233,8 +244,9 @@ Start with 1-2 skills. Add more as you notice patterns.
## Step 5: Add your tools via MCP (15 minutes per tool)
MCP servers connect Claude Code to external services.
The repo includes Playwright (browser). Here are the most
useful ones to add:
The repo includes Playwright (browser). Use `/mcp-integration`
from the plugin-dev plugin for guided setup of new servers.
Or add them manually:
### Slack (post messages, read channels)