CtrlK
BlogDocsLog inGet started
Tessl Logo

deepchat-release

Prepare and publish DeepChat releases in this repository. Use when Codex needs to bump the app version, update CHANGELOG.md, keep release notes bilingual from v1.0.1 onward with English bullets first and Chinese bullets second, run release checks, create or update versioned release branches such as release/v1.0.1, continue a half-finished release, fast-forward main with the documented release flow, create or push version tags, or clean up release branches after publishing.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, actionable release playbook with clear sequencing, validation checkpoints, and proper use of a one-level reference file. Its main weakness is mild repetition of the release-branch policy and publish flow across sections.

Suggestions

State the 'release/<version> is disposable' policy once in 'Follow Release Branch Policy' and reference it from the other sections instead of restating it in 'Choose The Release Mode' and 'Common Recovery Case'.

Merge the publish flow: mode 4 ('publish') and 'Follow Release Branch Policy' both describe the release:ff fast-forward; keep the exact command in one place and link to it.

Fold the 'Common Recovery Case' steps into modes 3 and 4, or reduce it to a pointer, since its numbered steps largely duplicate the update-existing-branch and publish modes.

DimensionReasoningScore

Conciseness

The body is action-oriented and free of concept bloat, but the disposable-release-branch policy and the release:ff publish flow are restated across 'Choose The Release Mode', 'Follow Release Branch Policy', and 'Common Recovery Case', so it could be tightened; not 3 because of this repetition, not 1 because nothing over-explains concepts Claude already knows.

2 / 3

Actionability

Provides concrete, copy-pasteable commands ('pnpm run format', 'pnpm run i18n', 'pnpm run lint', 'pnpm run release:ff -- release/<version> --tag v<version>') plus a pointer to the exact command checklist, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Four numbered release modes, explicit release checks as validation, a 'stop and ask before replacing it' checkpoint for wrong-commit tags, a force-with-lease guardrail, a PR-approval gate before publish, and a numbered recovery feedback loop; not capped at 2 because destructive operations do have verification steps.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that signals one-level-deep references clearly ('Use references/release-checklist.md for exact commands'), and that bundle file exists and is appropriately split from the overview.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that clearly states the skill's purpose and gives explicit, well-scoped triggers covering the full release lifecycle. It uses third-person/imperative voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'bump the app version, update CHANGELOG.md', 'create or update versioned release branches such as release/v1.0.1', 'fast-forward main', and 'create or push version tags', matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly states both what ('Prepare and publish DeepChat releases in this repository') and when ('Use when Codex needs to...') with explicit triggers, satisfying the both-what-and-when anchor; not 2 because the 'when' is explicit rather than implied.

3 / 3

Trigger Term Quality

Covers natural release vocabulary users would say ('bump the app version', 'update CHANGELOG.md', 'continue a half-finished release', 'clean up release branches'), and the body's Examples confirm real user phrasings; not reduced to 2 because common variations are well represented.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'DeepChat releases in this repository' with distinct triggers (versioned release branches, version tags, fast-forward flow), giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
ThinkInAIXYZ/deepchat
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.