CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

operator-closeout

Compatibility alias for the operations skill. Use only when the user explicitly invokes the older operator-closeout name; otherwise use operations for approval-gated operator work.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 a model of token-efficient redirect design: three unambiguous numbered instructions with an exact reference path, no duplicated procedure content, and no padding. It fully achieves its single purpose as a compatibility alias; the only unverifiable assumption is that the referenced operations skill exists at the stated path.

DimensionReasoningScore

Conciseness

The body is three lean lines ("Read and follow...", "Use `operations`...", "Do not maintain a second copy...") with zero padding or explanations of things Claude already knows; every token earns its place.

5 / 5

Actionability

For an instruction-only redirect skill, the guidance is fully executable: an exact path to read (`.agents/skills/operations/SKILL.md`), a concrete naming rule for documentation, and an explicit anti-duplication instruction — nothing is left vague. This assumes the referenced operations skill exists in the parent project, which cannot be verified from this bundle.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines, and the numbered 3-step sequence (read and follow the target, use the new name, don't duplicate the procedure) is unambiguous. No destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is a short, well-organized redirect with a single clearly signaled one-level-deep reference (the operations SKILL.md path) and no content that belongs in separate bundle files. The simple-skill exception applies: under 50 lines with no need for external references, well-organized sections merit a 5.

5 / 5

Total

20

/

20

Passed

Description

66%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 well-scoped compatibility-alias description that answers both what and when with an explicit, narrow trigger and strong disambiguation against the successor skill. Its main weakness is thin capability content: it says it is an alias without conveying what the underlying operations skill does, and it offers few natural trigger terms beyond the skill names themselves.

Suggestions

Add one clause stating what the underlying operations skill covers (e.g., "approval-gated operator work such as X and Y") so the 'what' is concrete rather than purely relational.

Include natural trigger variations users might say, such as "closeout" or "operator close-out", alongside the exact skill name to improve trigger-term coverage.

Consider naming the concrete behavior of the alias (e.g., "Delegates to the operations skill...") instead of only labeling it a "Compatibility alias".

DimensionReasoningScore

Specificity

"Compatibility alias for the operations skill" names the domain and its delegation function, but the description lists no concrete capability actions, sitting between the minimal-actions anchor (2) and the 1-2 concrete actions anchor (3). It states what it is rather than what concretely happens.

3 / 5

Completeness

Both parts are present: what ("Compatibility alias for the operations skill") and an explicit when ("Use only when the user explicitly invokes the older operator-closeout name; otherwise use operations"). The when is fully explicit, but the what only describes it as an alias-of without stating the underlying capability, so it falls between the 4 and 5 anchors.

4 / 5

Trigger Term Quality

The trigger term "operator-closeout" is explicitly captured ("when the user explicitly invokes the older operator-closeout name"), but coverage is limited to the two skill names with no natural variations or synonyms (e.g., "closeout", "operator close out"), matching the "some relevant keywords but missing common variations" anchor.

3 / 5

Distinctiveness Conflict Risk

The description is deliberately scoped to a single trigger (explicit invocation of the old name) and explicitly disambiguates toward "operations" in all other cases ("otherwise use operations for approval-gated operator work"), giving a clear niche with minimal conflict risk.

5 / 5

Total

15

/

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/operator-closeout/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.