learn
Skill38 starsChanged 2 months agoMITView on GitHub
Learn
195 other projects use a version of this.
Adopted by
Most recently taken up by
- todoist/todoist-clitheir own version, first seen Nov 15, 2026
- Doist/todoist-aitheir own version, first seen Nov 9, 2026
- Doist/todoist-clitheir own version, first seen Nov 8, 2026
- HughYau/AcademicForgetheir own version, first seen Nov 8, 2026
- dimsedra/skillstheir own version, first seen Nov 8, 2026
- rajanrx/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use add-anydoc, add-clidash and 10 more.
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.
TomGranotSkilladd-anydoc
Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
Also in 5 projects that use this
- TomGranotSkill
add-clidash
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Also in 5 projects that use this
seek888Skillopen-gstack-browser
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
Also in 11 projects that use this
Saqlain-811Skillios-sync
Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Also in 6 projects that use this
MicrosoftSkilladd-codex
Use Codex (CLI + AppServer) as the full agent provider — planning, tool orchestration, native compaction, MCP tools, session resume — in place of the Claude Agent SDK. ChatGPT subscription or OPENAI_API_KEY. Per-group via agent_provider. Distinct from using OpenAI as an MCP tool (where Claude remains the planner).
Also in 6 projects that use this
- MicrosoftSkill
add-deltachat
Add DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.
Also in 6 projects that use this
- +5 more from TomGranot
- +1 more from microsoft
Other versions195 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 195
- garrytan/gstack★ 141ksame name
- rohitg00/ai-engineering-from-scratch★ 78ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- tigerless-labs/autoharness★ 11ksame name
- tw93/claude-health★ 7.5ksame name
- tw93/Waza★ 7.5ksame name
- nykooi1/vibe-wise★ 3.5ksame name
- HughYau/AcademicForge★ 2.6ksame name
185 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.
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/autonomous_execution.mdcCursor rule
- .cursor/rules/cursor_rules_editing.mdcCursor rule
- .cursor/rules/cursor_rules_sync.mdcCursor rule
- .cursor/rules/cursor_rules_sync_requirement.mdcCursor rule
- site_pages/llms.txtllms.txt
- advisorySkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create_planSkill
- create-prototypeSkill
- create_prototypeSkill
- create_prSkill
- create-releaseSkill
- create_releaseSkill
- create-ruleSkill
- create_ruleSkill
- debugSkill
- draft-illustrationSkill
- draft_illustrationSkill
- endSkill
- evaluate_positioningSkill
- final-reviewSkill
- final_reviewSkill
- fix-feature-bugSkill
- fix_feature_bugSkill
- manage-error-debuggingSkill
- manage_error_debuggingSkill
- neversight_learn_skills.dev_obviously_awesomeSkill
- process_issuesSkill
- process_prsSkill
- publish-planSkill
- publish_planSkill
- publishSkill
- pullSkill
- pushSkill
- recover_sqlite_databaseSkill
- releaseSkill
- report-errorSkill
- report_errorSkill
- reportSkill
- reviewSkill
- run-feature-workflowSkill
- run_feature_workflowSkill
- setup-commandsSkill
- setup_commandsSkill
- setup-cursor-copiesSkill
- setup_cursor_copiesSkill
- store-neotomaSkill
- store_neotomaSkill
- sync-env-from-1passwordSkill
- sync_env_from_1passwordSkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create-prototypeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
11
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
- could be automatic: a setting could enforce it
- Distinctive: line 13
Use this skill when the user points out an omission, asks why something was not done, or requests stronger automatic behavior.
- Distinctive: line 35
Add explicit trigger language (when behavior must run).
- Distinctive: line 36
Add explicit ordering (what must happen first/next).
- Distinctive: line 37
Add forbidden patterns for the observed failure mode.
- Distinctive: line 38
Keep changes minimal and reusable.
- Distinctive: line 51
When the miss is release-quality related (for example "release notes missed npm-impacting runtime changes"), do all of the following:
- Distinctive: line 57
Update GitHub release notes with an explicit NPM Package Impact section.
- Distinctive: line 59
Verify by reading the release body after update.
- Distinctive: line 63
Do not commit changes unless user explicitly asks.
- Distinctive: line 64
Do not change generated copies when a source-of-truth file exists.
- Distinctive: line 65
Do not perform destructive operations without explicit user approval.
“Common” is measured: kept by at least 6 in 10 of the 170 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
<!-- Source: .cursor/skills/learn/SKILL.md -->Learn
Turn a behavior miss raised in chat into a permanent process improvement.
Use this skill when the user points out an omission, asks why something was not done, or requests stronger automatic behavior.
Goals
- Fix the immediate omission in the current turn.
- Prevent recurrence by updating the smallest durable artifact (rule, skill, or workflow doc).
- Apply the new guidance immediately in the same conversation.
Workflow
- Capture the miss
- Record expected behavior, actual behavior, and impact.
- Identify whether this is a one-off mistake or a recurring workflow gap.
- Neotoma:
/learnruns in normal chat — the full MCP turn lifecycle (bounded retrieval → user-phase store → edits/tools → reply → closing store) applies even when the fix is a one-line doc or rule tweak; "short pass" is never a waiver (seedocs/developer/mcp/instructions.md[TURN LIFECYCLE]).
- Choose the smallest durable artifact
- Rule: global repeated behavior.
- Skill: multi-step workflow behavior.
- Workflow doc/checklist: release/process quality gates.
- Hook/tooling: enforcement that should run automatically.
- Implement focused guidance
- Add explicit trigger language (when behavior must run).
- Add explicit ordering (what must happen first/next).
- Add forbidden patterns for the observed failure mode.
- Keep changes minimal and reusable; avoid broad rewrites.
- Validate and apply now
- Re-run the scenario that failed (or nearest equivalent).
- Perform the newly-required behavior in this chat before concluding.
- Report outcome
- What changed.
- Why this artifact was chosen.
- What behavior is now enforced.
GitHub Release Pattern
When the miss is release-quality related (for example "release notes missed npm-impacting runtime changes"), do all of the following:
- Inspect commit range for the release tag (for example
vX.Y.(Z-1)..vX.Y.Z). - Classify changes into:
- npm package/runtime impact (
src/,package.json,package-lock.json,README.md,openapi.yaml) - docs/site/process-only impact
- npm package/runtime impact (
- Update GitHub release notes with an explicit NPM Package Impact section.
- Include clear "changed/not changed" statements for API surface artifacts (notably
openapi.yaml). - Verify by reading the release body after update.
Constraints
- Do not commit changes unless user explicitly asks.
- Do not change generated copies when a source-of-truth file exists.
- Do not perform destructive operations without explicit user approval.
- For release-note fixes, prefer updating the existing GitHub release over creating duplicate releases.
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.