reasoning-controls
Use when adjusting reasoning depth, budgets, or metrics visibility - provides guidance for selecting and applying reasoning controls safely.
Profile →npx skills add majiayu000/claude-skill-registry --skill reasoning-controls --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Reasoning Controls ## Overview Control reasoning depth and cost trade-offs using consistent settings and metrics. ## When to Use - Adjusting reasoning depth or thinking mode - Setting budget limits for cost or latency - Reporting reasoning metrics Avoid when: - The task doesn’t require explicit reasoning controls ## Quick Reference | Task | Load reference | | --- | --- | | Adjust reasoning | `skills/reasoning-controls/references/adjust.md` | | Budget controls | `skills/reasoning-controls/references/budget.md` | | Metrics reporting | `skills/reasoning-controls/references/metrics.md` | ## Workflow 1. Determine the control goal (depth, budget, metrics). 2. Load the matching reference. 3. Apply the control with the appropriate parameters. 4. Report settings and effects. ## Output - Updated reasoning settings - Metrics or confirmation output ## Common Mistakes - Over-allocating budget for simple tasks - Changing depth without explaining trade-offs
- Overview
- When to Use
- Quick Reference
- Workflow
- Output
- Common Mistakes
What does the reasoning-controls skill do?
Use when adjusting reasoning depth, budgets, or metrics visibility - provides guidance for selecting and applying reasoning controls safely.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill reasoning-controls --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.