north-star-synthesis
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Converge all accumulated context into a crystallized North Star statement and structured ResearchBrief. Performs self-review before presenting to user. Use as the final tactic in any start mode — this is where everything comes together.
In this repository32 other files it gives its agents.
- actor-profilingSkill
- and-or-decomposeSkill
- ask-constraintsSkill
- ask-decomposition-validationSkill
- ask-intentionalitySkill
- ask-obstacle-acceptanceSkill
- assess-obstacle-severitySkill
- broad-paper-searchSkill
- broad-web-searchSkill
- clarify-resourcesSkill
- cold-startSkill
- crystallize-north-starSkill
- deep-web-searchSkill
- direction-narrowingSkill
- explore-resumeSkill
- feasibility-checkSkill
- final-validationSkill
- formulate-top-goalSkill
- generate-candidate-fieldsSkill
- generate-research-briefSkill
- goal-decompositionSkill
- hot-startSkill
- identify-obstaclesSkill
- landscape-reconnaissanceSkill
- landscape-synthesisSkill
- north-star-crystallizationSkill
- obstacle-analysisSkill
- present-and-askSkill
- present-candidatesSkill
- propose-mitigationsSkill
- validate-leavesSkill
- warm-startSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 27
If self-review finds issues: return to specific tactic/SOP for targeted fix (not full re-run)
- Distinctive: line 28
If passes: present North Star + ResearchBrief to user
≈ “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
North Star Synthesis
Converge all accumulated context into North Star + ResearchBrief.
Available SOPs
| SOP | Purpose | Execution |
| crystallize-north-star | Formulate the North Star statement with user | dialogue |
| generate-research-brief | Aggregate all context into structured ResearchBrief | subagent |
| final-validation | Self-review + present to user for confirmation | dialogue |
Methodology Guidance
crystallize-north-starchecks: specific? ambitious? achievable?generate-research-briefaggregates all context (ActorProfile, FieldPanorama, RankedCandidates, ObstacleReport, GoalTree, North Star, key references, key terms)final-validationperforms self-review before presenting:- Placeholder scan: any TBD / empty sections?
- Internal consistency: do sections contradict?
- Completeness: critical information gaps?
- Ambiguity: statements interpretable two ways?
- If self-review finds issues: return to specific tactic/SOP for targeted fix (not full re-run)
- If passes: present North Star + ResearchBrief to user
Output (Tactic-Level Aggregation, Presented to User)
North Star (one sentence) + ResearchBrief (structured context document)
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.