Agent skill
your-skill-name
Replace with when the AI should activate this skill. Be pushy — cover multiple phrasings so the AI activates for a wide range of user prompts.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/template-affitor-affiliate-skills
Metadata
Additional technical details for this skill
- stage
- SX-StageName
- author
- your-github-handle
- version
- 1.0
SKILL.md
Your Skill Name
What this skill does in 2-3 sentences. Focus on the outcome, not the process.
Stage
This skill belongs to Stage SX: StageName
When to Use
- Scenario 1
- Scenario 2
- Scenario 3
Input Schema
{
required_field: { # (required) Description
name: string # Example value
}
optional_field: string # (optional, default: "value") Description
}
Workflow
Step 1: Gather Context
What to check first. How to handle missing inputs.
Step 2: Execute Core Task
The main work the skill does.
Step 3: Format and Deliver
How to structure the output.
Output Schema
Other skills can consume these fields from conversation context:
{
primary_output: string # Main result for downstream chaining
secondary_output: string # Additional data for downstream skills
}
Output Format
## [Skill Name]: [Context]
### Section 1
[Main content]
### Section 2
[Supporting content]
Error Handling
- Missing required input: How to recover gracefully.
- External data unavailable: Fallback strategy.
- Edge case: How to handle unexpected scenarios.
Examples
Example 1: [realistic user prompt] → [step-by-step what the skill does] → [expected output summary]
Example 2: [different scenario] → [step-by-step] → [expected output summary]
Example 3: [edge case or beginner scenario] → [step-by-step] → [expected output summary]
Flywheel Connections
Feeds Into
[skill](S[X]) — [what data/output flows forward to this skill]
Fed By
[skill](S[X]) — [what data/output flows back from this skill]
Feedback Loop
- [analytics metric or data point that improves this skill's next run]
Quality Gate
Include this section for content-producing skills (S2, S3, S4, S5, S7). Remove for non-content skills.
Before delivering output, verify:
- Would I share this on MY personal social?
- Contains specific, surprising detail? (not generic)
- Respects reader's intelligence?
- Remarkable enough to share? (Purple Cow test)
- Irresistible offer framing? (if S4 offer skills ran)
Any NO → rewrite before delivering. Do not flag this checklist to the user.
Volume Mode
Include this section for S2 Content skills only. Remove for other stages.
When mode: "volume":
- Generate 5-10 variations instead of 1
- Prioritize speed + variety over perfection
- Tag each with variant ID for A/B tracking
- Let data pick the winner (GaryVee philosophy)
volume_output:
variants:
- id: string # e.g., "v1", "v2"
content: string # The variation
angle: string # What makes this one different
References
references/your-reference.md— description of what it containsshared/references/ftc-compliance.md— FTC disclosure requirementsshared/references/affitor-branding.md— branding rulesshared/references/flywheel-connections.md— master flywheel connection map
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?