Agent skill
ic-explain
Explain IC10 code behavior in plain English. Use when user pastes IC10 code and asks what it does, how it works, or wants to understand existing Stationeers scripts.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/ic-explain
SKILL.md
IC10 Code Explanation
Explain IC10 code behavior in clear, understandable language.
Workflow
-
Analysis Phase Use Task tool to spawn:
code-analyzer- Analyze code structure, execution flow, and behavior
-
Explanation Phase Take the analysis output and create a human-readable explanation
Instructions
When the user asks to explain IC10 code:
-
Launch
code-analyzeragent with the provided code -
From the analysis, create a clear explanation that includes:
- Overview: 1-2 sentences describing what the code does
- Device Setup: What devices need to be connected where
- How It Works: Step-by-step explanation of the logic
- Key Behaviors: What happens under different conditions
-
Keep the explanation accessible:
- Use plain language, not just code terms
- Relate to real-world behavior (e.g., "when pressure is too high")
- Highlight important thresholds and values
-
If issues are found, mention them but don't fix (that's for ic-debug)
Example Triggers
- "What does this code do?"
- "Explain this script"
- "How does this work?"
- "Can you walk me through this?"
- "I don't understand this code"
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?