bk-monitor-tapd-summary
获取 TAPD 待办单据并生成归纳总结。当用户提到获取 TAPD 单据、查看待办时使用。
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./bcs-services/bcs-project-manager/.cursor/skills/bk-monitor-tapd-summary/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is functional with a clear 'Use when' clause and specific tool reference (TAPD), making it easy to distinguish from other skills. However, it could benefit from more specific action details and additional trigger term variations that users might naturally use when requesting TAPD-related tasks.
Suggestions
Add more specific actions like '查看需求状态', '统计任务进度', or '导出报告' to improve specificity
Include additional trigger term variations such as 'TAPD任务', '工作项', '需求', 'backlog' to improve keyword coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TAPD) and two actions (获取待办单据/get pending items, 生成归纳总结/generate summary), but lacks comprehensive detail about what specific operations or outputs are supported. | 2 / 3 |
Completeness | Clearly answers both what (获取TAPD待办单据并生成归纳总结) and when (当用户提到获取TAPD单据、查看待办时使用) with explicit trigger guidance using '当...时使用' pattern. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'TAPD 单据' and '待办', but missing common variations users might say such as 'TAPD任务', '工作项', 'backlog', or '需求列表'. | 2 / 3 |
Distinctiveness Conflict Risk | TAPD is a specific project management tool, making this skill clearly distinguishable from generic document or task management skills. The explicit mention of TAPD creates a clear niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized and concise, with a clear 4-step workflow and appropriate use of external references. However, it lacks executable code examples and validation checkpoints, relying heavily on external files for implementation details. The duplicate '可用资源' section should be removed.
Suggestions
Add executable code examples or specific API call syntax in Step 1 instead of just naming the functions
Include validation/error handling guidance for API failures (e.g., what to do if stories_get returns empty or errors)
Remove the duplicate '📦 可用资源' section at the end
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, with no unnecessary explanations. Each section serves a clear purpose and assumes Claude understands the domain concepts. | 3 / 3 |
Actionability | Provides clear workflow steps and references specific API calls (stories_get, bugs_get, tasks_get), but lacks executable code examples. The actual implementation details are deferred to external files. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-4), but lacks validation checkpoints. No explicit error handling or feedback loops for API failures or data processing issues. | 2 / 3 |
Progressive Disclosure | Good structure with clear overview and well-signaled one-level-deep references to mcp-calls.md, status-mapping.md, and summary-template.md. Content is appropriately split. | 3 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- TencentBlueKing/bk-bcs
- Commit
b08ac38
- 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.