Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From majestic-tools
Provides structure templates for four skill archetypes: CLI reference, methodology, safety/security, and orchestration. Use when creating new Claude Code skills.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-toolsHow this skill is triggered — by the user, by Claude, or both
Slash command
/majestic-tools:skill-archetypesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Identify which archetype fits best and follow its structure.
Design and iterate Claude Code skills: SKILL.md structure, description formulas, content architecture, and quality evaluation. Invoke whenever task involves any interaction with Claude Code skills — creating, reviewing, evaluating, debugging, or improving skills.
Creates SKILL.md files following the Agent Skills open standard (agentskills.io). Covers frontmatter schema, procedure writing with Expected/On failure pairs, validation checklists, and registry integration.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends OpenCode's capabilities with specialized knowledge, workflows, or tool integrations.
Share bugs, ideas, or general feedback.
Identify which archetype fits best and follow its structure.
For tools, CLIs, APIs. Structure by operations, minimize prose.
## Authentication
[How to authenticate]
## Core Operations
| Command | Description |
|---------|-------------|
| `tool init` | Initialize project |
| `tool run` | Execute task |
## Common Workflows
[Task-oriented examples]
Examples: kamal-coder, wrangler-coder, gh-cli
For development practices, workflows, philosophies.
## Core Philosophy
[Why this approach matters - 2-3 sentences max]
## The Process
1. [Step with criteria]
2. [Step with criteria]
## Decision Criteria
| Situation | Action |
|-----------|--------|
| [condition] | [response] |
Examples: tdd-workflow, dhh-coder, founder-mode
For operations with risk. Include tiered approvals.
## Risk Tiers
| Tier | Operations | Approval |
|------|------------|----------|
| Low | Read-only queries | Auto |
| Medium | Modifications | Confirm |
| High | Destructive ops | Explicit |
## Blocking Patterns
[What to never do]
## Allowing Patterns
[Safe operations]
Examples: infra-security-review, devops-verifier
For multi-step processes that coordinate other tools.
## Quick Start
[Minimal invocation]
## Workflow Phases
1. [Phase]: [What happens]
2. [Phase]: [What happens]
## Machine-Readable Output
[JSON/YAML schema for automation]
Examples: build-task-workflow, quality-gate
For reproducible agent-to-agent handoffs, encode prompts in ALL CAPS:
## THE EXACT PROMPT
ANALYZE THE FOLLOWING CODE FOR SECURITY VULNERABILITIES:
1. CHECK FOR HARDCODED SECRETS
2. IDENTIFY SQL INJECTION RISKS
3. FLAG INSECURE DEPENDENCIES
RETURN FINDINGS AS JSON WITH SEVERITY LEVELS.
For multi-step processes with progress tracking:
## Checklist
- [ ] Step 1: [Action with success criteria]
- [ ] Step 2: [Action with success criteria]
- [ ] Step 3: [Action with success criteria]
Mark each complete before proceeding.
For operations requiring validation:
## Validation Loop
1. Execute action
2. Verify result matches criteria
3. If FAIL: diagnose → fix → goto 1
4. If PASS: proceed to next step
Never advance without validation passing.