MicrosoftKnown publishermicrosoft/PilotSwarm/packages/sdk/examples/repo-workspaces/seed/home/.github/skills/notes/SKILL.mdnotes
Skill14 starsChanged 8 months agoMITView on GitHub
Keep dated notes in your own folder, so later sessions can pick up where earlier ones stopped.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Keep notes in notes/ in your folder: one file per day, notes/YYYY-MM-DD.md.
- Distinctive: line 13
Add to the end of the day's file.
- Distinctive: line 14
Start each entry with the time (UTC) and a one-line topic.
- Distinctive: line 15
Before starting a task, read the last two days of notes.
“Common” is measured: kept by at least 6 in 10 of the 14 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
Notes
Your own folder is shared by all your sessions. It is the working folder
when no repo is attached, and extra folder "home" when one is;
get_session_workspace shows its path.
- Keep notes in
notes/in your folder: one file per day,notes/YYYY-MM-DD.md. - Add to the end of the day's file. Do not rewrite earlier entries.
- Start each entry with the time (UTC) and a one-line topic.
- Before starting a task, read the last two days of notes.
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- blogminhquy/javis-os★ 505same name
- howells/fiction★ 19same name
- DaniilBrusnikUa/claude-code-handoff★ 9same name
- adeonir/agent-skills★ 8same name
- phanghonghao/THU-Awesome-Skills★ 8same name
- baney75/myelinate★ 4same name
- DoKu67/claude-code-skils★ 4same name
- jholhewres/devclaw-skills★ 4same name
- TTflysky/sirenhuisuo★ 4same name
- speech115/notes-skill★ 2same name
10 more not listed
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.
Used alongsideProjects with it also use brainstorm.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicodianskSkillbrainstorm
Use when the user asks to add, build or change a feature and hasn't said exactly how, including a one-line request such as "add JSON output to the list command". Sizes the request first - a clear quick fix gets done directly, and anything with open choices is explored with questions before any code.
Also in 4 projects that use this
In this repository50 other files it gives its agents.
- packages/sdk/examples/repo-workspaces/seed/home/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-repair-loopSkill
- duroxide-orchestration-versioningSkill
- editorial-standardsSkill
- finance-research-standardsSkill
- valuation-methodsSkill
- pilotswarm-architectureSkill
- deployment-safetySkill
- incident-responseSkill
- add-activitySkill
- add-eventSkill
- add-testSkill
- add-toolSkill
- agent-versioningSkill
- azure-ps-test-runner-vmSkill
- debug-orchestrationSkill
- debug-testSkill
- horizondb-idiosyncrasiesSkill
- horizon-facts-eval-sweepSkill
- investigate-duroxide-runtimeSkill
- pilotswarm-aks-deploySkill
- pilotswarm-aks-resetSkill
- pilotswarm-new-env-deploySkill
- pilotswarm-perfSkill
- pilotswarm-portal-app-regSkill
- pilotswarm-portal-auth-assignmentsSkill
- pilotswarm-releaseSkill
- pilotswarm-tuiSkill
- pilotswarm-vpn-client-profileSkill
- schema-migrationSkill
- share-a-fileSkill
- cost-latency-analysisSkill
- graph-debugSkill
- orchestration-session-lifecycleSkill
- resourcemgrSkill
- sweeperSkill
- canvas-appsSkill
- html-visualsSkill
- pilotswarm-agent-versioningSkill
- pilotswarm-aks-identitySkill
- pilotswarm-azure-deployerSkill
- pilotswarm-azure-lessonsSkill
- pilotswarm-cli-builderSkill
- pilotswarm-duroxide-versioningSkill
- pilotswarm-hybrid-datastoreSkill
- pilotswarm-knowledge-harvesterSkill
- pilotswarm-portal-builderSkill
- pilotswarm-sdk-builderSkill
- pilotswarm-three-tierSkill
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.