reframe
Skill1 starsChanged 16 days agoMITView on GitHub
Form a brief for requested reframing or as Goal Swarm's goal-formation step. Use the user's request and context to establish the outcome, methods, constraints, evaluation, and finish line.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Belweave/hstacktheir own version, first seen Nov 8, 2026
- callumflack/skillstheir own version, first seen Nov 1, 2026
- killi1812/man-mcptheir own version, first seen Oct 8, 2026
- Kshitijpalsinghtomar/depth-skillstheir own version, first seen Oct 1, 2026
- bloxy-studios/shorts-studiotheir own version, first seen Oct 1, 2026
- Lengros/bennutheir own version, first seen Jul 8, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- ramboz/jig★ 7same name
- rohunvora/my-claude-skills★ 6same name
- Kshitijpalsinghtomar/depth-skills★ 5same name
- Lengros/bennu★ 2same name
- Belweave/hstack★ 1same name
- callumflack/skills★ 1same name
- killi1812/man-mcp★ 1same name
- bloxy-studios/shorts-studio★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-loginSkill
- animateSkill
- app-intentsSkill
- app-store-connectSkill
- architectSkill
- arenaSkill
- blast-radiusSkill
- codebase-designSkill
- code-qualitySkill
- correctSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- eli5Skill
- engineering-principlesSkill
- gauntlet-loopSkill
- gh-stackSkill
- goal-swarmSkill
- grillingSkill
- grill-with-docsSkill
- handoffSkill
- howSkill
- improve-codebase-architectureSkill
- ios-hapticsSkill
- koubouSkill
- mergeSkill
- orchestrationSkill
- prototypeSkill
- prSkill
- react-best-practicesSkill
- react-doctorSkill
- repo-cleanupSkill
- researchSkill
- retroSkill
- review-fix-loopSkill
- reviewSkill
- review-sweepSkill
- seoSkill
- setup-sreestackSkill
- show-dont-tellSkill
- showroomSkill
- snipsnap-do-choresSkill
- snip-snapSkill
- swift-testing-modernizationSkill
- swiftuiSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- ui-designSkill
- uikitSkill
- verifySkill
- wayfinderSkill
- web-component-inspirationSkill
- whySkill
- writing-for-agentsSkill
- xcode-security-auditSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the request, settled decisions, and relevant project evidence.
- Distinctive: line 21
Consider the dimensions that can improve this task:
- Distinctive: line 35
Use Research for factual uncertainty worth investigating.
- Distinctive: line 36
Use experiments to settle empirical questions within the requested scope.
- Distinctive: line 37
Keep ambitious targets distinct from evidence that they have been achieved.
- Distinctive: line 47
When another workflow calls Reframe, return the brief to that owner.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reframe
Form a brief worth executing from the user's request and context. Preserve explicit requirements while considering stronger ways to achieve the outcome. Scale the pass to what is unsettled: a precise request may need only a concise confirmation. Reframing alone ends with the brief.
Find the better task
Read the request, settled decisions, and relevant project evidence. Separate the desired result from the proposed means or artifact. Keep alternatives beyond authorized scope labeled as proposals. Use Verify's acceptance guidance to resolve what context can establish and ask for material user decisions.
Consider the dimensions that can improve this task:
- Outcome: who needs what change, and what decision or activity does the requested artifact serve? Identify a higher-level outcome when it helps.
- Depth: which original inputs, expert methods, and instruments would make the work more rigorous? Name the method rather than an expert persona.
- Range: which adjacent field handles the same kind of problem, and which of its concrete techniques transfers here?
- Evaluation: how and by whom should the result be judged, which constraints must hold, and what finish line was requested? Use the acceptance guidance to propose suitable checks or qualitative criteria, leaving uncertainty and missing prerequisites explicit.
Choose the strongest coherent framing rather than expanding every dimension. Use Research for factual uncertainty worth investigating. Use experiments to settle empirical questions within the requested scope. Keep ambitious targets distinct from evidence that they have been achieved.
Return the brief
State the outcome and target, scope and preserved constraints, relevant methods, evaluation, and requested finish line. Include material assumptions and unknowns; explain meaningful framing changes. Proposed evaluation is not evidence that the result has been achieved. Reuse the existing format and task record; a clear request can be confirmed in a few sentences without a separate document.
When another workflow calls Reframe, return the brief to that owner. The owner continues execution; do not start another copy of its workflow. In particular, Goal Swarm consumes the brief and keeps ownership of the goal.
For a direct reframing request, return the brief in chat unless another format or destination was requested. If the user also requested execution, continue through the authorized workflow with that brief. Requested goal or swarm execution uses Goal Swarm, passing the formed brief so it can be reused. Reframing alone authorizes no implementation, native goal, schedule, or external action.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

