amcs-{SKILL_NAME}-{ACTION}
{ONE_SENTENCE_PURPOSE}. Use when {TRIGGER_CONDITION}.
Best use case
amcs-{SKILL_NAME}-{ACTION} is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
{ONE_SENTENCE_PURPOSE}. Use when {TRIGGER_CONDITION}.
Teams using amcs-{SKILL_NAME}-{ACTION} should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/amcs-skill_name-action/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How amcs-{SKILL_NAME}-{ACTION} Compares
| Feature / Agent | amcs-{SKILL_NAME}-{ACTION} | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
{ONE_SENTENCE_PURPOSE}. Use when {TRIGGER_CONDITION}.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AMCS {Skill Title}
{2-3 sentence overview of what this skill does and why it exists in the AMCS workflow.}
## When to Use
Invoke this skill {POSITION_IN_WORKFLOW} when {CONDITION}. This node {RUNS_IN_PARALLEL/SEQUENTIALLY} with {OTHER_NODES} and feeds into {DOWNSTREAM_NODES}.
## Input Contract
```yaml
inputs:
- name: {input_1_name}
type: {schema_reference} # e.g., amcs://schemas/sds-1.0.json
required: true/false
description: {What this input provides}
- name: {input_2_name}
type: {type}
required: true/false
description: {What this input provides}
- name: seed
type: integer
required: true
description: Determinism seed (use seed+{NODE_INDEX} for this node)
```
## Output Contract
```yaml
outputs:
- name: {output_name}
type: {schema_reference}
description: |
{Multi-line description of output structure}
- field_1: {description}
- field_2: {description}
- _hash: SHA-256 hash for provenance tracking
```
## Determinism Requirements
- **Seed**: `run_seed + {NODE_INDEX}` for any stochastic operations
- **Temperature**: {VALUE} (or N/A if no LLM generation)
- **Top-p**: {VALUE} (or N/A)
- **Retrieval**: {NONE | Pinned by content hash}
- **Hashing**: Hash final output for provenance tracking
- **Key Invariant**: Same inputs + seed => identical outputs
## Constraints & Policies
{List all constraints this skill must enforce}
- {CONSTRAINT_1}: {RULE}
- {CONSTRAINT_2}: {RULE}
- {POLICY_1}: {ENFORCEMENT}
- {VALIDATION_1}: {CHECKS}
Example:
- Tempo MUST fall within blueprint's `tempo_range` for primary genre
- Tags MUST NOT conflict per `taxonomies/tag_conflict_matrix.json`
- Profanity filter applies to all text fields
- Maximum {X} {ITEMS} to avoid {PROBLEM}
## Implementation Guidance
{Detailed step-by-step implementation instructions}
### Step 1: {First Major Step}
{Detailed instructions for this step}
1. {Sub-step 1}
2. {Sub-step 2}
3. {Sub-step 3}
**Example**:
```python
# Code example showing pattern
```
### Step 2: {Second Major Step}
{Detailed instructions}
**Algorithm**:
1. {Algorithm step}
2. {Algorithm step}
3. Score = {FORMULA}
**Target**: {THRESHOLD}
**Example**:
```
{Concrete example with data}
```
**Issues**:
- If {CONDITION}: `"{ERROR_MESSAGE}"`
### Step {N}: Validate and Return
1. Validate output against `{SCHEMA_REFERENCE}`
2. Compute SHA-256 hash of output
3. Return output with hash in metadata
**Example Output**:
```json
{
"{field}": "{value}",
"_hash": "abc123...",
"_metadata": {}
}
```
## Examples
### Example 1: {Typical Use Case}
**Input**:
```json
{
"{input_field}": "{value}",
"seed": 42
}
```
**Output**:
```json
{
"{output_field}": "{value}",
"_hash": "abc123..."
}
```
### Example 2: {Edge Case or Variation}
**Input**:
```json
{
"{input_field}": "{different_value}",
"seed": 100
}
```
**Output**:
```json
{
"{output_field}": "{result}",
"_hash": "def456..."
}
```
### Example 3: {Error Case}
**Input**:
```json
{
"{invalid_input}": "{bad_value}"
}
```
**Expected Error**:
```
ValueError: {ERROR_MESSAGE}
```
## Testing
### Basic Functionality Test
Test that the skill produces valid output for typical inputs.
### Determinism Test
Critical: Run with same inputs + seed 10 times, verify identical outputs.
**Test Pattern**:
```python
@pytest.mark.parametrize("run_number", range(10))
async def test_{skill}_determinism(sample_input, context, run_number):
result = await {skill_function}(sample_input, context)
if run_number == 0:
pytest.first_hash = result["_hash"]
assert result["_hash"] == pytest.first_hash
```
### Input Validation Test
Test that invalid inputs are rejected with clear error messages.
### Policy Enforcement Test
Test that constraints and policies are properly enforced.
## Common Pitfalls
1. **{Pitfall 1}**: {Description of what goes wrong and how to avoid}
2. **{Pitfall 2}**: {Description}
3. **{Pitfall 3}**: {Description}
4. **Determinism Loss**: {What breaks determinism in this skill}
5. **Hash Omission**: Missing provenance hash breaks traceability
## Troubleshooting
### Issue: {Common Problem}
**Symptoms**: {What the user sees}
**Cause**: {Why this happens}
**Solution**: {How to fix it}
### Issue: Determinism Test Failing
**Symptoms**: Different outputs from same inputs + seed
**Cause**:
- Unseeded randomness
- Non-deterministic retrieval
- Datetime dependencies
- High temperature/top-p
**Solution**:
- Use `context.seed` for all random operations
- Pin retrieval by content hash
- Remove datetime.now() calls
- Set temperature ≤ 0.3, top_p ≤ 0.9
## Related Skills
- **{UPSTREAM_SKILL}**: Provides inputs to this skill
- **{DOWNSTREAM_SKILL}**: Consumes outputs from this skill
- **{PARALLEL_SKILL}**: Runs in parallel with this skill
## References
- PRD: `docs/project_plans/PRDs/{prd_file}.prd.md`
- Workflow: `docs/project_plans/PRDs/claude_code_orchestration.prd.md` (section {X})
- Blueprint: `docs/hit_song_blueprint/AI/{genre}_blueprint.md`
- Schema: `schemas/{schema_name}.json`Related Skills
rename-method
Refactoring technique to improve code readability by renaming methods to better reflect their purpose and functionality
namecheap
Domain registration and management via Namecheap API.
domain-name-brainstormer
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
compaction-advisor
Provides context-aware compaction guidance with intelligent checkpointing. Monitors context during long tasks and suggests checkpoints before compaction interrupts your work.
add-reaction
Slack メッセージにリアクションを追加する。「リアクション追加」「リアクションつけて」「👍つけて」「絵文字で反応」「リアクションで返信」「いいねして」「リアクション送って」などで起動。User Token があればユーザーとしてリアクション、なければ Bot としてリアクション。
actions-pattern
Garante que novas Actions sigam o padrão de classes actions reutilizáveis do Easy Budget.
actionbook
This skill should be used when the user needs to automate multi-step website tasks. Activates for browser automation, web scraping, UI testing, or building AI agents. Provides complete action manuals with step-by-step instructions and verified selectors.
actionable-review-format-standards
Standardized output format for code reviews with severity labels, file:line references, and fix code snippets. Use when generating review reports that need consistent, actionable feedback structure.
action-policy-coder
Use proactively for authorization with ActionPolicy. Creates policies, scopes, and integrates with GraphQL/ActionCable. Preferred over Pundit for composable, cacheable authorization.
Action Pattern Conventions
This skill should be used when the user asks about "Laravel action pattern", "action class naming", "how to structure actions", "React component patterns", "Node.js service structure", "framework-specific conventions", or discusses creating reusable, focused classes following action pattern conventions in Laravel, Symfony, React, Vue, or Node.js projects.
action-mapping-designer
This skill should be used when ensuring training focuses on performance outcomes and business impact. Use this skill to identify essential content, design performance-focused activities, create job aids, and eliminate unnecessary training.
action-item-organizer
Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.