CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chinese-indie-dev

处理 1c7/chinese-independent-developer 仓库的项目提交。 检查 issue #160 新评论、新开的 Issue、新开的 PR, 将有效项目添加到对应 README,关闭垃圾内容,并把评论区的意见与建议上报维护者。 历史判例与事故记录在同目录的 references/precedents.md,遇到边界判断时按需查阅。 当用户要求“收录项目”“处理提交”“处理 issue”“跑一下列表”或运行中国独立开发者列表维护流程时使用。

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, well-sequenced operational runbook: every phase has executable commands, explicit validation checkpoints, feedback loops, and verbatim templates, and the precedent library is correctly externalized as a one-level, on-demand reference with a navigation map. The one weakness is token efficiency — several inline incident anecdotes and duplicated rules inflate the body and would sit more appropriately in references/precedents.md.

Suggestions

Move the inline date-stamped incident anecdotes (the 2026-09-27 capacity anecdote, the 2026-10-21 SliceLoft cross-posting story, the 2026-11-01/2026-10-29 maintainer quotes) into the corresponding sections of references/precedents.md and keep only the rule plus a '→ 判例:X' pointer in the body, as the skill itself already prescribes.

State each rule once: '每一次拒绝都必须出现在最终汇报里' and the no-reaction/no-deletion constraints currently appear in both the 硬红线 section and their detailed sections — keep the red-line listing as the checklist and drop the restatements, or vice versa.

The env self-check and portability notes in 0.1/10 (e.g. the Homebrew PATH export) could be folded into a single preflight block to remove cross-referencing between sections.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout (no explanations of git/gh/jq concepts) but includes more than minor trimmable material: five-plus inline date-stamped incident narratives (e.g. "2026-09-27 实测:开跑时已是 490,082 字节…", "2026-10-21 事故:SliceLoft 的致谢被贴到 Issue #1622…", the 2026-11-01 and 2026-10-29 maintainer quotes) that belong in the precedent library, plus rules restated two-to-three times across sections (rejection reporting appears in red line 8, section 4, and section 9). This is 'mostly efficient but could be tightened' rather than 'minor instances of over-explanation', since the skill already maintains references/precedents.md for exactly this case history.

3 / 5

Actionability

Nearly everything is copy-paste executable: concrete pipelines ("gh api …/issues/160/comments?since=$SINCE&per_page=100 | tee /tmp/c160.json | jq 'length'"), the full PR conflict-resolution command sequence, link-check invocations ("python3 .github/scripts/check_links.py"), platform-portable date handling, and verbatim Chinese/English rejection, thanks, and final-report templates. Common and edge cases are both covered, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The workflow is explicitly sequenced (预检 → 检查一/一之二 → 检查二 → 检查三 → 身份判断 → 拒绝类别 → 通用处理 → 致谢 → 收尾扫描 → 汇报) with hard-stop preconditions ("必须为空", "必须是 0"), validation at every mutation (POST → PATCH → GET, comment-id reverse lookup against cross-posting, jq -e scan validation with exit 1), and genuine feedback loops (re-scan until residual 0, merge retry after sleep 5, 3-try scan retries). The 硬红线 section acts as a checklist, matching the anchor with explicit validation, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

The split follows a stated, sensible criterion — body is process and hard constraints read fully each run, while "历史判例与事故记录在同目录的 references/precedents.md,遇到边界判断时按需查阅" with an explicit instruction not to bulk-load it. The reference is one level deep, pointers appear inline at point of need ("→ 判例:X"), the file exists with sections A–M matching every pointer, and note 10 provides a complete navigation map of the library sections.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description: it enumerates the full set of concrete actions for a named repository and workflow, and closes with an explicit use-when clause containing five natural trigger phrases including colloquial variants. The only gap is that a few plausible user phrasings (e.g. about handling PRs specifically) are absent from the trigger list.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "检查 issue #160 新评论、新开的 Issue、新开的 PR,将有效项目添加到对应 README,关闭垃圾内容,并把评论区的意见与建议上报维护者" — covering all phases of the workflow (check three sources, add valid entries, close spam, report feedback), which matches the comprehensive-coverage anchor rather than the 'several actions, minor gaps' anchor below it.

5 / 5

Completeness

Both questions are answered explicitly: 'what' via the enumerated actions (check #160 comments/issues/PRs, add to README, close spam, report feedback) and 'when' via "当用户要求…时使用" with concrete trigger phrases, exactly matching the anchor for clearly and explicitly answering both with concrete triggers.

5 / 5

Trigger Term Quality

Five natural trigger phrases are given — "收录项目"、"处理提交"、"处理 issue"、"跑一下列表"、"运行中国独立开发者列表维护流程" — including the colloquial "跑一下列表", giving good keyword coverage. A few natural variants users might say (e.g. "处理一下新 PR"、"看下新投稿") are not covered, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The description names a specific repository ("1c7/chinese-independent-developer") and a specific issue number (#160), giving it a clear niche with distinct triggers and virtually zero risk of firing for an unrelated skill — stronger than the 'minor overlap risk' anchor at 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

Total

15

/

16

Passed

Repository

1c7/chinese-independent-developer

Path

.claude/skills/chinese-indie-dev/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.