CtrlK
BlogDocsLog inGet started
Tessl Logo

opencreator-bug-fix

读取 OpenCreator 固定飞书 Bug 文档,识别最新日期、今天或用户指定日期下尚未处理的问题,在当前 OpenCreator 仓库按文档顺序逐项验证、修复和测试,把原因分析与修复方法精确回写到原问题下,并在每个问题闭环后创建独立 Git commit,直到目标范围内的问题全部完成或遇到明确阻塞。用于“处理 Bug 文档”“修复今天新增问题”“继续处理飞书问题”“重新验证某日期问题”等 OpenCreator 日常缺陷、体验问题和明确优化建议。

73

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

81%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.

A well-structured, highly actionable workflow with strong validation feedback loops appropriate to its batch/auto-commit nature. Main weaknesses are minor repetition of the stopping/blocking rules and incomplete command syntax for the Feishu block writeback operations.

Suggestions

Consolidate the 'complete all issues / allowed early-stop / blocking' rules into one section and reference it elsewhere to remove the repeated restatements in 选择处理范围, 逐问题执行, and 最终汇报.

Provide a full copy-paste lark-cli command for block_insert_after / block_replace (with --doc, --as user, --revision-id, and the block-id placeholder), mirroring the executable fetch examples.

Consider moving the detailed lark-cli fetch/writeback command reference into a references/ file so the SKILL.md body reads as a tighter overview pointing to one-level-deep details.

DimensionReasoningScore

Conciseness

Largely lean instruction that assumes Claude's competence (no concept explanations), but the 'complete all issues / blocking-stop' rules are restated across 选择处理范围, 逐问题执行, and 最终汇报 and could be tightened.

4 / 5

Actionability

Gives concrete, executable commands (lark-cli auth/fetch, git status/diff --cached, commit format) and an XML writeback template, but the block_insert_after / block_replace writeback operations are named without full lark-cli invocation syntax.

4 / 5

Workflow Clarity

A top-level flowchart, numbered per-issue steps, and explicit validation checkpoints (auth verify before edits, 回读确认 after writeback, test selection, no-commit-on-verify-failure) with feedback loops and clear blocking rules fit the batch/destructive checklist anchor.

5 / 5

Progressive Disclosure

Well-organized into clear sections with no nested or buried references and no monolithic API wall, but at ~200 lines with no external files, the lark-cli command details could optionally be split into a reference for cleaner overview navigation.

4 / 5

Total

17

/

20

Passed

Description

100%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 strong, third-person description that pairs a concrete end-to-end action set with explicit '用于' trigger phrases and a well-scoped niche. It avoids fluff and clearly states both capability and activation conditions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 读取文档、识别未处理问题、验证、修复、测试、回写原因分析与修复方法、创建独立 Git commit — covering the full bug-fix loop comprehensively rather than naming the domain alone.

5 / 5

Completeness

Explicitly answers both what (read doc, triage, verify, fix, test, write back, commit) and when, via a concrete '用于...' trigger clause listing distinct invocation scenarios.

5 / 5

Trigger Term Quality

Provides several natural trigger phrases users would actually say ('处理 Bug 文档''修复今天新增问题''继续处理飞书问题''重新验证某日期问题') plus category terms 缺陷/体验问题/优化建议, giving broad keyword coverage.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche — OpenCreator bugs tracked in a fixed Feishu doc — with triggers referencing Feishu/OpenCreator that are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
krillinai/OpenCreator
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.