advanced-features-2025 — Claude Code skill: features and install
The advanced-features-2025 skill covers plugin hooks, MCP setup, and repository-level team distribution. Use it when building or configuring Claude Code plugins for a team.
MIT 159 installs ★ 66 updated 2026-06-18
npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a claude-codeWhat advanced-features-2025 does
The skill explains progressive loading: startup metadata identifies when a skill applies, its main instructions load on activation, and files in references/ provide deeper detail on demand. It outlines a layout with SKILL.md, references/, examples/, and scripts/.
Hook examples show PreToolUse checks before a tool runs and PostToolUse actions such as running tests after file changes. Other sections cover MCP configuration in .mcp.json and team plugin setup through .claude/settings.json. The MCP examples pass API keys through environment variables.
The guidance favors specific hook matchers and recommends testing scripts independently; use .* sparingly. That broad matcher can run a hook for any tool, so choose it deliberately.
What it helps with
- Split skill instructions into loading tiers
- Run checks before or after tool calls
- Configure an MCP server through
.mcp.json - Set up repository-level plugin distribution for a team
Example prompts for the agent
- Show me how to configure
PreToolUseandPostToolUsehooks for command checks and post-edit tests. - Explain how to add an MCP server in
.mcp.jsonand pass its API key through an environment variable. - Draft a team plugin setup using
.claude/settings.json.
How to install advanced-features-2025
1Skills CLI (Vercel)
npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a claude-code2Manually: put the files in place
~/.claude/skills/advanced-features-2025/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/advanced-features-2025/
1Skills CLI (Vercel)
npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a codex2Manually: put the files in place
.agents/skills/advanced-features-2025/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a cursor2Manually: put the files in place
.cursor/skills/advanced-features-2025/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install JosiahSiegel/claude-plugin-marketplace plugins/plugin-master/skills/advanced-features-20252Manually: put the files in place
.github/skills/advanced-features-2025/SKILL.md1Skills CLI (Vercel)
npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a gemini-cli2Platform CLI
gemini skills install https://github.com/JosiahSiegel/claude-plugin-marketplace --path plugins/plugin-master/skills/advanced-features-2025Manually: put the files in place
.devin/skills/advanced-features-2025/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about advanced-features-2025
How do I install advanced-features-2025 in Claude Code?
Run npx skills add JosiahSiegel/claude-plugin-marketplace --skill advanced-features-2025 -a claude-code. The skill file is available at ~/.claude/skills/advanced-features-2025/SKILL.md.
What does advanced-features-2025 do?
It guides you through plugin hooks, MCP server configuration, and repository-based team distribution. It also explains how to load skill content progressively.
How does advanced-features-2025 recommend configuring hooks?
Use specific matchers, such as Write|Edit, and test hook scripts on their own. The guide advises using .* sparingly.
Source text
SKILL.md · MIT
---
name: advanced-features-2025
description: |
Advanced Claude Code plugin features for hooks, MCP integration, team distribution, and progressive disclosure.
PROACTIVELY activate for: (1) progressive disclosure design, (2) hook automation, (3) PreToolUse and PostToolUse hooks, (4) MCP server integration, (5) .mcp.json configuration, (6) team plugin distribution, (7) repository-level plugin layouts, (8) context efficiency, (9) private marketplaces, (10) ${CLAUDE_PLUGIN_ROOT}.
Provides: hooks reference, MCP patterns, team distribution, and context-efficiency guidance.
---
# Advanced Plugin Features (2025)
## Quick Reference
| Feature | Location | Purpose |
|---------|----------|---------|
| Agent Skills | `skills/*/SKILL.md` | Dynamic knowledge loading |
| Hooks | `hooks/hooks.json` | Event automation |
| MCP Servers | `.mcp.json` | External integrations |
| Team Config | `.claude/settings.json` | Repository plugins |
| Hook Event | When Fired | Use Case |
|------------|------------|----------|
| PreToolUse | Before tool | Validation |
| PostToolUse | After tool | Testing, linting |
| SessionStart | Session begins | Logging, setup |
| SessionEnd | Session ends | Cleanup |
| UserPromptSubmit | Prompt submitted | Preprocessing |
| PreCompact | Before compact | State save |
| Notification | Notification shown | Custom alerts |
| Stop | User stops | Cleanup |
| SubagentStop | Subagent ends | Logging |
| Variable | Purpose |
|----------|---------|
| `${CLAUDE_PLUGIN_ROOT}` | Plugin installation path |
| `${TOOL_INPUT_*}` | Tool input parameters |
## Agent Skills
### Concept
Skills are dynamically loaded based on task context, enabling:
- **Unbounded capacity**: Knowledge split across files
- **Context efficiency**: Only load what's needed
- **Progressive disclosure**: Three-tier loading
### Three-Tier Loading
1. **Frontmatter**: Loaded at startup (triggers)
2. **SKILL.md body**: Loaded on activation
3. **references/**: Loaded when detail needed
### Structure
```text
skills/
└── skill-name/
├── SKILL.md # Core content
├── references/ # Detailed docs
│ └── deep-dive.md
├── examples/ # Working code
│ └── example.md
└── scripts/ # Utilities
└── tool.sh
```
### SKILL.md Format
```markdown
---
name: skill-name
description: |
When to activate this skill. Include:
(1) Use case 1
(2) Use case 2
Provides: what it offers
---
# Skill Title
## Quick Reference
[Tables, key points]
## Core Content
[Essential information - keep lean]
## Additional Resources
See `references/` for detailed guidance.
```
## Hooks
### Configuration
**Inline in plugin.json:**
```json
{
"hooks": {
"PostToolUse": [{
"matcher": "Write|Edit",
"hooks": [{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/lint.sh"
}]
}]
}
}
```
**Separate hooks.json:**
```json
{
"PostToolUse": [{
"matcher": "Write",
"hooks": [{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/format.sh",
"timeout": 5000
}]
}]
}
```
### Matchers
- `Write` - File writes
- `Edit` - File edits
- `Bash` - Shell commands
- `Write|Edit` - Multiple tools
- `.*` - Any tool (use sparingly)
### Common Patterns
**Auto-test after changes:**
```json
{
"PostToolUse": [{
"matcher": "Write|Edit",
"hooks": [{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/run-tests.sh"
}]
}]
}
```
**Validate before Bash:**
```json
{
"PreToolUse": [{
"matcher": "Bash",
"hooks": [{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/validate-cmd.sh"
}]
}]
}
```
## MCP Server Integration
### Configuration
```json
{
"mcpServers": {
"server-name": {
"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp/server.js"],
"env": {
"API_KEY": "${API_KEY}"
}
}
}
}
```
### External Services
```json
{
"mcpServers": {
"stripe": {
"command": "npx",
"args": ["-y", "@stripe/mcp-server"],
"env": {
"STRIPE_API_KEY": "${STRIPE_API_KEY}"
}
}
}
}
```
## Repository Configuration
### Team Distribution
Create `.claude/settings.json` at repo root:
```json
{
"extraKnownMarketplaces": [
"company/internal-plugins"
],
"plugins": {
"enabled": [
"deployment-helper@company",
"code-standards@company"
]
}
}
```
### Workflow
1. Maintainer creates `.claude/settings.json`
2. Team members clone repo
3. Trust folder when prompted
4. Plugins install automatically
## Best Practices
### Progressive Disclosure
- Keep SKILL.md under 500 lines
- Move details to `references/`
- Use `examples/` for working code
- Reference files with relative paths
### Hooks
- Use specific matchers (avoid `.*`)
- Set reasonable timeouts
- Use `${CLAUDE_PLUGIN_ROOT}` for paths
- Test scripts independently
### MCP
- Document required env vars
- Provide setup instructions
- Use environment variables for secrets
- Test connection before distribution
## Additional Resources
For detailed patterns, see:
- **`references/hooks-advanced.md`** - Complete hook patterns
- **`references/mcp-patterns.md`** - MCP integration examples
- **`references/team-distribution.md`** - Repository configuration
- **`examples/hook-scripts.md`** - Working hook scripts
© JosiahSiegel · MIT · JosiahSiegel/claude-plugin-marketplace