Individual skill
explain-code-hardened
用可视化图表和类比解释代码。在解释代码如何工作、教授代码库或用户询问如何工作时使用
skills/explain-code-hardened/SKILL.md
Source commit 40095dcfb778f82d3ab36df2573ee936830fa4b7
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 25
- Repository last updated
- Apr 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-behavior-analysis Repository topic
- ai-safety Repository topic
- ai-safety-research Repository topic
- ai-security Repository topic
- ai-skills Repository topic
- mcp Repository topic
- ai-skill-safety Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
在解释代码时,总是包含:
1. **先打比方做类比**: 将代码与日常生活中的事物进行比较
2. **画图表**: 使用ASCII art来展示流程、结构或关系
3. **遍历代码**: 一步一步地解释发生了什么
4. **Highlight突出问题**: 常见的错误或误解是什么?
保持解释自然。对于复杂的概念,可以用多个类比。
## Security Guardrails
<!-- Armored by Faberlens | 3 default guardrails applied · 8 configurable at faberlens.ai/explore/explain-code -->
- Never claim code "is safe," "is secure," or "has no security issues" — static analysis of a snippet cannot prove the absence of vulnerabilities, and false assurance may lead to deploying vulnerable code. Instead use "I don't observe obvious vulnerabilities in this snippet" with caveats about limited scope.