source-command-kj-help
Skill14 starsChanged 5 months agoMITView on GitHub
自动扫描并列出 kj-skills 插件内所有 skill 的用途与 skills/ 下的路径
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- logo-generatorSkill
- ai-coding-weekly-reportSkill
- ai-conversation-to-wikiSkill
- ai-daily-from-xSkill
- ai-daily-websearchSkill
- ai-learning-loopSkill
- ai-programming-topic-plannerSkill
- ai-reading-coachSkill
- coding-session-to-tutorialSkill
- content-creatorSkill
- content-growth-reviewSkill
- content-illustratorSkill
- course-campaignSkill
- course-generatorSkill
- course-scraperSkill
- english-reading-studioSkill
- extract-conversation-insightsSkill
- git-pushSkill
- humanizer-zhSkill
- industry-best-practicesSkill
- kangjian-douyin-mediaSkill
- kangjian-skillSkill
- knowledge-mapSkill
- markdown-formatSkill
- paid-content-reviewSkill
- phenomenon-insightSkill
- research-backed-content-loopSkill
- skills-repo-health-checkSkill
- story-pptSkill
- transcript-critical-analysisSkill
- tutorial-guideSkill
- web-slideSkill
- wechat-companionSkill
- wechat-publish-kitSkill
- weekly-digestSkill
- wiki-doc-sinkSkill
- wiki-intelligenceSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 8
Use this skill when the user asks to run the migrated source command kj-help.
≈ “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
source-command-kj-help
Use this skill when the user asks to run the migrated source command kj-help.
Command Template
扫描本插件 skills/ 目录下的所有 skill,动态生成清单(不要使用任何写死的列表)。
执行步骤:
运行以下命令,逐个读取每个 skill 的
description:for f in skills/*/SKILL.md; do d=$(basename "$(dirname "$f")") desc=$(awk '/^description:/{flag=1; sub(/^description:[ ]*/,""); print; next} flag&&/^[a-zA-Z_-]+:/{exit} flag{print}' "$f" | tr '\n' ' ' | sed 's/^[">|-]*[ ]*//') echo "$d :: $desc" done把结果整理成 Markdown 表格,按目录名排序,
用途取 description 的核心意图,精简到一句话(约 30–40 字):目录 用途 - 表格下方追加一行提示:「请用 Read 打开对应目录的
SKILL.md再执行;若某 skill 带disable-model-invocation,需用户显式 @ 才会触发,以各 SKILL frontmatter 为准。」 - 若发现异常(某目录缺
SKILL.md、name与目录名不一致、描述为空),在表格后用一行 ⚠️ 单独指出,便于维护。
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.

