connect-the-dots
Skill1 starsChanged 8 months agoMITView on GitHub
Use when new notes, inputs, or research items need to be connected into an existing knowledge graph or operating context. Helps turn scattered information into structure, patterns, and useful links.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zinan92/skills-repotheir own version, first seen Mar 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zinan92/skills-repo★ 1same 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 repository5 other files it gives its agents.
- agent-onboardingSkill
- brainstormingSkill
- canvas-communicationSkill
- verification-before-completionSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 8
Use this skill when information exists, but the structure does not.
- Distinctive: line 28
Read the new material.
- Distinctive: line 31
Add links, tags, or placement.
- Distinctive: line 33
If a broader pattern emerges, write that pattern down explicitly.
- Distinctive: line 38
no duplicate weak notes when one strong note is enough
- Distinctive: line 39
no promotion of low-value material into curated memory
- Distinctive: line 40
prefer compression and connection over accumulation
≈ “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
Connect the Dots
Use this skill when information exists, but the structure does not.
Core Job
Take scattered notes, inputs, or observations and answer:
- where does this belong
- what does it connect to
- is it worth keeping
- what pattern does it reinforce or challenge
When To Use
- adding a new note into a knowledge graph
- connecting a new research item to existing themes
- updating an index, map, or hub note
- deciding whether something should be promoted into curated memory
Workflow
- Read the new material.
- Determine whether it is worth keeping.
- Identify the most relevant existing notes or categories.
- Add links, tags, or placement.
- Summarize the connection in one or two useful sentences.
- If a broader pattern emerges, write that pattern down explicitly.
Quality Rules
- no orphan notes
- no duplicate weak notes when one strong note is enough
- no promotion of low-value material into curated memory
- prefer compression and connection over accumulation
Output Standard
A good result should make the system easier to scan, not harder.
Prefer:
- one canonical note
- clear links
- a short rationale for why the note matters
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.