explaining-code
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.
git clone --depth 1 https://github.com/Geeksfino/openskills /tmp/explaining-code && cp -r /tmp/explaining-code/examples/skills/explaining-code ~/.claude/skills/explaining-codeSKILL.md
# Code Explanation Skill When explaining code, follow this structure: ## 1. Overview Start with a one-sentence summary of what the code does. ## 2. Key Concepts Identify and explain any important concepts, patterns, or techniques used. ## 3. Line-by-Line Breakdown Walk through the code section by section, explaining: - What each part does - Why it's written that way - Any edge cases or gotchas ## 4. Examples If helpful, provide examples of how the code would behave with different inputs. ## 5. Related Concepts Mention related concepts the user might want to learn about next. ## Style Guidelines - Use simple language, avoiding jargon unless necessary - When using technical terms, define them briefly - Use analogies when they help clarify complex concepts - Format code snippets with syntax highlighting - Be thorough but concise
Maintain compatibility between openskills-runtime and language bindings (TypeScript, Python), including feature flags, build configuration, and smoke verification.
Route OpenSkills development tasks to the right project skill or subagent, including sequencing rules for debugging, feature work, regression checks, and release readiness.
Run deterministic OpenSkills end-to-end validation across runtime tests and example agents, then report tool calls, activation behavior, and regressions.
Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.
Prepare and validate OpenSkills release readiness across runtime, bindings, examples, and regression gates with a deterministic checklist and go/no-go outcome.
Diagnose openskills-runtime execution failures in sandboxed paths (Landlock, seatbelt, native script execution, wasm execution) and produce root-cause-first findings with minimal-risk remediation steps.
Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.
Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.