Use BEFORE generating, refactoring, reviewing, or debugging code. Trigger phrases include "write a function/script/class for X", "review this code/diff/PR", "refactor this", "debug this error", "is this implementation correct", "what's wrong with this code", "improve this code", "translate from X to Y", or any prompt with a code block the user wants you to act on. Also fires when planning architectural changes, picking algorithms or data structures, or evaluating dependency upgrades. Calls the code MCP tool to retrieve an engineering scaffold (failure pattern, procedure, correct-pattern example, verification step) before generating. Catches hallucinated APIs, lost edge cases, premature algorithm commitment, silent contract violations, refactors that change behavior masked by passing tests. Do NOT trigger for pure code reading with no action requested, simple syntax questions, file system operations, running existing tests, or confirming an existing pattern is fine.
Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.
读取 https://funcoding.ai/skills/jeremylongshore/tons-of-skills-marketplace/ejentum-code/install.md ，按里面的步骤帮我安装这个 Skill。
When this skill triggers, call the code tool from the ejentum MCP server. Pass a 1-2 sentence framing of WHAT you are coding or reviewing as the query argument. Include the failure risk to avoid where possible.
Good query: review a Python refactor that converts raise UserNotFound to silent default return; tests still pass
Bad query: look at this code
The tool returns a structured scaffold containing:
[CODE FAILURE]: engineering failure pattern to avoid[ENGINEERING PROCEDURE]: steps to follow[REASONING TOPOLOGY]: decision flow[CORRECT PATTERN]: shape correct code should take[VERIFICATION]: self-checkAmplify: and Suppress: signalsAbsorb internally. Do NOT echo bracket labels in the user-facing reply. Apply the scaffold's failure-pattern check against your draft before responding; if your code exhibits the named failure, rewrite.
If the API is unreachable, proceed with native engineering. The scaffold enhances; it is not a hard dependency.
Latency cost: ~1 second. Benefit: catches the kinds of behavioral changes and silent contract violations that look plausible but break under real conditions.
anthropics/skills180kCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Testing
DietrichGebert/ponytail158kQuality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.
Testing
DietrichGebert/ponytail158kQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.
Testing
DietrichGebert/ponytail158kQuality review of a diff: bugs, security, real load, missing tests, speed, and what to delete. Each finding says what goes wrong and how to fix it.
Testing
addyosmani/agent-skills103kAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Testing
addyosmani/agent-skills103kRefines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".
Testing