CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release

Assemble PsychSift release-readiness evidence, risk-scoped local checks, governance proof, rollback notes, and approval-gated final verification. Use for release, merge readiness, production handoff, or go-live confidence.

Quality

84%

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

78%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 disciplined, token-efficient orchestration skill with a clear sequenced workflow and strong safety gating around destructive commands. Its main weakness is actionability: the pivotal step ('run the flight plan', 'smallest focused checks') references project artifacts without defining or locating them, and there is no guidance for handling failed checks.

Suggestions

Define or point to 'the flight plan' (e.g., a repo path like docs/flight-plan.md or an inline checklist) so step 2's core action is executable without guessing.

Enumerate the candidate 'focused checks' or reference where they are defined, mirroring how the proof types (UI, clinical, RAG, migration, privacy, deployment) are already listed.

Add a brief failure-handling loop: what to do when a check fails (fix and re-run vs. report and mark not-ready) before returning the ready/not-ready decision.

DimensionReasoningScore

Conciseness

Fifteen lean lines with zero concept explanation — every sentence instructs ('Inspect intended diff...', 'Do not run verify:release... without approval') and the AGENTS.md boundary note is stated in one sentence. Fully matches the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete anchors exist (`npm run verify:pr-local`, `verify:release`, `AGENTS.md`, named artifacts like review ledger and migrations), but the core execution step — 'Run the flight plan and complete the smallest focused checks' — leaves both the flight plan and the candidate checks undefined, so Claude cannot execute step 2 without guessing.

3 / 5

Workflow Clarity

A clear 6-step sequence (inspect → checks → conditional proofs → governance → gated commands → decision) with an approval gate on destructive commands and a decision output enumerating passed/failed/skipped/gated. Below the 5 anchor because there is no failure-handling loop (what to do when a check fails before deciding).

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files exist, and the content is well organized (header, boundary note, numbered list) with the one external pointer (`AGENTS.md`) clearly signaled inline. Meets the simple-skill exception for a full score.

5 / 5

Total

17

/

20

Passed

Description

83%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 description: third-person, concise, concrete about deliverables, and with an explicit 'Use for' trigger clause covering four realistic scenarios. The only gaps are a few missing synonyms (deploy/ship/launch) and not mentioning the ready/not-ready decision output that the body delivers.

DimensionReasoningScore

Specificity

Lists several concrete deliverables — 'release-readiness evidence, risk-scoped local checks, governance proof, rollback notes, and approval-gated final verification' — giving specific coverage of the release domain. Falls short of the 5 anchor because the decision output (ready/not-ready) and how checks are selected are not described.

4 / 5

Completeness

Explicitly answers both: what ('Assemble... evidence, risk-scoped local checks, governance proof, rollback notes, and approval-gated final verification') and when ('Use for release, merge readiness, production handoff, or go-live confidence') with concrete trigger phrases. Matches the anchor-5 good example structure.

5 / 5

Trigger Term Quality

'Use for release, merge readiness, production handoff, or go-live confidence' provides good natural trigger phrases a user would say. A few common variations are missing (e.g., 'deploy', 'ship', 'launch', 'rollout'), keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Anchored to the PsychSift project with domain-specific terms (governance proof, rollback notes, clinical/RAG context implied), giving a clear niche. Minor overlap risk remains with generic PR-publication or code-review skills triggered by 'release' or 'merge readiness'.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

.agents/skills/release/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.