Use BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include "should I X or Y", "why is X happening", "what's the best approach", "what are the tradeoffs", "help me think through", "diagnose", "root cause", "plan/design X", "what are the implications of", "compare these approaches". Also fires on cross-domain analysis, strategy questions, architecture decisions, or anything requiring multiple factors to be weighed before responding. The skill calls the reasoning MCP tool to retrieve a cognitive scaffold (named failure pattern, executable procedure, suppression vectors, falsification test) the model absorbs internally before generating its response. Catches causal shortcuts, premature conclusions, generic templates, and surface pattern matching that produce confidently-wrong answers. Do NOT trigger for simple factual lookups, syntax questions, file reads, code execution, or restating the user's input.
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-reasoning/install.md ，按里面的步骤帮我安装这个 Skill。
When this skill triggers, call the reasoning tool from the ejentum MCP server. Pass a 1-2 sentence framing of WHAT you are reasoning about as the query argument. Be specific about the task, not what tool you want.
Good query: diagnose why a microservice returns 503s under load
Bad query: help me think
The tool returns a structured scaffold containing:
[NEGATIVE GATE]: failure pattern to avoid[PROCEDURE]: steps to follow[REASONING TOPOLOGY]: decision flow with gates and traps[TARGET PATTERN]: correct shape your reasoning should take[FALSIFICATION TEST]: self-check criterionAmplify: signals to engageSuppress: failure modes to blockAbsorb the scaffold internally and shape your response with it. The bracketed fields are instructions, not content to display. Do NOT echo the bracket labels, do NOT name the topology, do NOT meta-comment on calling the tool. The user-facing reply is naturally phrased and shaped by the injection.
If the API is unreachable or returns an error, proceed with native reasoning. The scaffold enhances; it is not a hard dependency.
Latency cost: ~1 second. Benefit: reasoning quality the model cannot reliably reproduce on its own for non-trivial tasks.
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