CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

operations

Turn pending PsychSift operator, provisioning, configuration, and provider work into a deduplicated dependency-ordered batch with explicit approvals and evidence. Use for operator debt, manual runbooks, or deferred external actions.

Quality

86%

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

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

Lean, highly actionable instructions that sequence a batch-operations workflow with explicit approval and rollback awareness. The only notable gap is the absence of an explicit validation feedback loop and a concrete output format for the recorded batch items.

DimensionReasoningScore

Conciseness

Six terse numbered steps with zero padding, no explanation of concepts Claude already knows, and every token earning its place. Not below 5 because nothing could be cut without losing guidance.

5 / 5

Actionability

Provides a concrete executable command ('npm run workflow:operator-closeout -- --write-evidence') and a specific per-item field checklist (owner, command, expected result, evidence, rollback). Not 5 because steps 2-6 give no output format, location, or example of the recorded batch, leaving minor gaps.

4 / 5

Workflow Clarity

Clear six-step sequence with an explicit approval checkpoint ('Ask for approval only when the batch is precise enough to execute safely') and named verification/rollback stages. Not 5 because the validate -> fix -> retry feedback loop is only implicit for a batch-execution skill, and not 3 because validation, approval gating, and rollback are explicitly present.

4 / 5

Progressive Disclosure

A 13-line single-file skill with a well-organized numbered list and no need for external references; per the simple-skill guidance this warrants a 5. No bundle files exist to reference.

5 / 5

Total

18

/

20

Passed

Description

80%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, domain-anchored description with a clear what and an explicit 'Use for' trigger clause. Its main weakness is jargon-dense trigger terms that miss natural user phrasings and synonyms.

Suggestions

Add one or two natural-language trigger phrases users would actually say, e.g., 'Use when closing out pending ops tasks, finishing a release, or when manual runbook steps are left undone'.

Soften jargon in the trigger clause with synonyms for 'operator debt' and 'deferred external actions' so the description matches how users phrase the need.

Slightly expand the 'what' with one more plain-language action (e.g., 'produces a reviewable checklist') to reduce reliance on compressed terms like 'dependency-ordered batch'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'deduplicated dependency-ordered batch with explicit approvals and evidence' — with minor gaps such as the generic 'provider work'. Not 5 because coverage of what the skill does is compressed into jargon rather than a comprehensive action list.

4 / 5

Completeness

Explicitly answers both: 'what' (turn pending operator/provisioning/configuration/provider work into a deduplicated, dependency-ordered batch with approvals and evidence) and 'when' ('Use for operator debt, manual runbooks, or deferred external actions'). Not 4 because the when-clause is explicit with concrete trigger phrases rather than weakly specified.

5 / 5

Trigger Term Quality

'operator debt', 'manual runbooks', 'deferred external actions' are relevant domain keywords, but they are jargon-heavy and lack common variations or synonyms a user might naturally say. Not 4 because there are no broader natural phrasings (e.g., 'pending ops tasks', 'closeout', 'infrastructure setup').

3 / 5

Distinctiveness Conflict Risk

The 'PsychSift operator' niche and specific trigger terms give it a clear, distinct scope with minimal conflict risk against general skills. Not 4 because no realistic overlapping-skill scenario is identifiable within or outside the project.

5 / 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/operations/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.