frames
Skill2 starsChanged 51 days agoMITView on GitHub
Synthesize a set of signal cards into frames — named narrative groupings such as drivers of change, tensions, or emerging themes — each with a title, summary, body and the signals it binds, many-to-many. Use when the user asks "what are the themes", "drivers of change", "cluster these signals", "what's the story here", "frames", or needs the layer between raw signals and a report. Stage: structure.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- sanmidable/skillstheir own version, first seen Nov 8, 2026
- raphaelsalaja/skillstheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- raphaelsalaja/skills★ 62same name
- sanmidable/skills★ 2same 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 repository16 other files it gives its agents.
- adjacency-scanSkill
- artifact-from-the-futureSkill
- competitive-scanSkill
- grill-the-futureSkill
- groundSkill
- horizon-scanSkill
- implicationsSkill
- innovation-radarSkill
- mergeSkill
- regulatory-scanSkill
- reportSkill
- risk-radarSkill
- scenariosSkill
- scopeSkill
- signalSkill
- technology-scanSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read first: ../../core/signal-schema.md, ../../core/envisioning.md, ../../core/voice.md.
- Distinctive: line 46
Append, don't replace: If a frame set already exists for this scope, new frames are added alongside.
- Very specific: line 76
No forecasts inside frames.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
frames
A frame is a narrative that several signals belong to. Frames are how a scan becomes readable without losing the cards underneath: every claim in a frame points back to the signals that support it.
Read first: ../../core/signal-schema.md, ../../core/envisioning.md,
../../core/voice.md.
Input
Active signal cards (a scan index, folder, or list; frozen merged_into
cards are skipped), and a frame kind. Default kinds:
| kind | a frame is… | good count |
drivers | a force pushing the scope in one direction | 4–7 |
tensions | two forces pulling against each other | 3–5 |
themes | a pattern several signals share | 5–8 |
bets | a claim the corpus supports that a strategist could act on | 3–5 |
The user can name another kind; write its definition into the output.
Procedure
- Read every card. Frames come from the What and So what sections, not the titles.
- Propose frames. Each needs at least two signals; a one-signal frame is that signal restated. A signal may sit in several frames — that is the point of many-to-many, and a signal in three frames is usually the most important one in the corpus.
- Write each frame:
title— 3–6 words, a claim not a topic ("Regulators move before standards bodies", not "Regulation").summary— two sentences, present tense.content— 150–250 words: the mechanism, the actors, the evidence, with each signal cited inline by slug the first time it is used.signals[]— the bound cards.
- Check coverage. List signals bound to no frame. Either they are noise (say so) or a frame is missing (add it). Don't force them in.
- Append, don't replace. If a frame set already exists for this scope, new frames are added alongside; existing ones are edited only when the user asks. Provenance is the version history.
- Persist to
/foresight/frames/<scope>-<kind>(category: research), or./foresight/frames/.message:frames · <kind> · <n> frames.
Output
---
kind: frames
frame_kind: <drivers|tensions|themes|bets|custom>
title: <scope> · <frame kind>
scope:
sources: [<scan index or cards>]
signals_total: <n>
signals_unbound: [<slugs>]
---
## <frame title>
<summary>
<content>
**Signals:** slug · slug · slugRefusals
- Fewer than 6 active cards → say a frame set won't be meaningful; offer
to run a scan or
signalfirst. - No forecasts inside frames. A frame describes what the signals show
now;
scenariosis where futures live.
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.