learning-blog
Skill0 starsChanged 6 months agoMITView on GitHub
根据一次开发、排错或学习过程生成结构化学习笔记。Use when the user asks to write a learning blog, record what was learned, summarize a tool setup, create a troubleshooting note, or preserve a reusable explanation from the conversation.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-config-maintainerSkill
- coderSkill
- engineer-coder-orchestratorSkill
- engineerSkill
- github-repo-standardsSkill
- unity6-projectSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Write a markdown note under LearningBlog/YYYY-MM-DD-{slug}.md when the project uses that folder.
- Distinctive: line 17
Update the nearest index file if one exists.
- Distinctive: line 21
Prefer concise Chinese explanations.
- Very specific: line 22
Use powershell, bash, csharp, json, or other accurate code fence languages.
- Distinctive: line 23
Use troubleshooting tables with columns: 现象 / 原因 / 解决。
- Distinctive: line 24
Do not store API keys, tokens, passwords, private URLs, or raw secrets.
- Very specific: line 28
Use docs/templates/learning-blog-template.md when available.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Learning Blog
Workflow
- Identify the topic, date, and intended depth.
- Extract only useful material from the current conversation and local artifacts:
- commands used
- errors and fixes
- concepts learned
- final verification state
- Write a markdown note under
LearningBlog/YYYY-MM-DD-{slug}.mdwhen the project uses that folder; otherwise ask or place it underdocs/notes/. - Update the nearest index file if one exists.
Style
- Prefer concise Chinese explanations.
- Use
powershell,bash,csharp,json, or other accurate code fence languages. - Use troubleshooting tables with columns: 现象 / 原因 / 解决。
- Do not store API keys, tokens, passwords, private URLs, or raw secrets.
Template
Use docs/templates/learning-blog-template.md when available.
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.

