devops

DevOps 能力索引。Git、测试、DevSecOps、数据库。当用户提到 DevOps、CI/CD、Git、测试时路由到此。

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./templates/skills/domains/devops/SKILL.md

Quality

Content

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

The body is concise and well-structured as an index, but it offers no executable guidance or workflow and its seven sub-skill links point to .md files that are not present in the bundle, making the progressive-disclosure references non-functional. It reads as a skeleton router rather than a complete skill body.

Suggestions

Either ship the seven referenced sub-skill .md files (git-workflow.md, testing.md, devsecops.md, database.md, performance.md, observability.md, cost-optimization.md) or remove the links so references are not dangling.

Add at least one concrete, actionable starting point (e.g. a representative command or a 'when X, jump to file Y' decision rule) so the body is actionable rather than only descriptive.

For each sub-skill row, add a one-line trigger that tells Claude when to follow that link, giving the matrix a navigable workflow rather than a flat list.

Dimension	Reasoning	Score
Conciseness	The body is short and lean — a capability matrix table plus a compact principles block — with no padding or explanations of concepts Claude already knows; minor cosmetic flourishes (emoji header) keep it just above the lean-5 anchor at 4.	4 / 5
Actionability	It lists sub-skills with categories but provides no concrete commands, code, or executable steps — only high-level hints about what each sub-skill covers, matching 'minimal concrete guidance; high-level hints but missing the specific steps'.	2 / 5
Workflow Clarity	There is no multi-step process or sequence; the body is an index with no workflow, validation, or checkpoints. As a router it lacks any sequencing beyond the table, fitting 'rough sequence present but many gaps; steps poorly defined' at best — 2.	2 / 5
Progressive Disclosure	The matrix links to seven .md files (git-workflow.md, testing.md, etc.) but none of those files exist in the bundle, so the references are dangling; per the guideline to score against actual bundle structure, broken/buried references cap this low — 2.	2 / 5
	Total	10 / 20 Passed

Description

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

The description is a concise router/index that names its domains and gives an explicit routing trigger, but it lists categories rather than concrete actions and relies on broad trigger terms that overlap with its own sub-skills. It is functional but not comprehensive or sharply distinct.

Suggestions

Add a couple of concrete actions per domain (e.g. '审查 PR、写测试、扫描依赖、优化 SQL') to lift specificity beyond a category list.

Broaden trigger terms with natural synonyms (e.g. 部署/deployment, 监控/monitoring, 流水线/pipeline) so the description matches what users actually say.

Tighten distinctiveness by framing it as a router explicitly (e.g. 'Use this router first when a request spans multiple DevOps areas') to reduce overlap with the sub-skills it routes to.

Dimension	Reasoning	Score
Specificity	Names the domain (Git, testing, DevSecOps, database) and the routing action, but lists categories rather than concrete actions per category, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	The 'what' (DevOps 能力索引 / router) is clear and the 'when' is explicitly stated via the routing clause, but the when is a routing trigger rather than a usage scenario; on re-read it sits at the boundary of 3 and 4 — explicit when present but somewhat weak, so 3.	3 / 5
Trigger Term Quality	Includes natural user-facing terms (DevOps, CI/CD, Git, 测试), but missing common variations/synonyms like 'deployment', 'monitoring', or file extensions; fits 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	As an index/router it is somewhat distinct, but broad DevOps triggers (CI/CD, Git, 测试) overlap with the very sub-skills it routes to; fits 'somewhat specific but could still overlap'.	3 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 7 missing	Warning

	Total	15 / 16 Passed

Repository: fengshao1227/ccg-workflow
Path: templates/skills/domains/devops/SKILL.md
Commit: f349e3d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.