CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical

Assemble clinical safety, privacy, source-governance, rollback, and production-readiness evidence for PsychSift changes. Use for answer generation, retrieval, ingestion, clinical content, source rendering, or other patient-safety-sensitive behavior.

Quality

81%

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

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

An extremely token-efficient clinical review checklist that is well-structured for its small size and free of padding. Its weakness is execution depth: the checks state what to enforce but not how to verify any of them, leaving both actionability and workflow validation implicit. Adding concrete verification steps or evidence expectations would lift the two 3-scores without hurting conciseness.

Suggestions

For each checklist item, add one concrete verification step — e.g. where to inspect for keyword bans, which tests or files evidence 'conservative failure behavior', and what artifact demonstrates the traced claim path.

Turn the list into a light ordered review workflow with explicit pass/fail criteria per item so completion is unambiguous.

Include a short example of the expected evidence summary output so 'assemble evidence' has a concrete deliverable shape.

DimensionReasoningScore

Conciseness

The 14-line body is lean and every line states a project-specific requirement ('transparent reference aid model (MDCalc / UpToDate)', 'live Supabase, OpenAI ... approval-gated'); nothing explains concepts Claude already knows and nothing is padded. Every token earns its place, matching anchor 5, and there is no verbosity to place it lower.

5 / 5

Actionability

Items name concrete anchors ('MDCalc / UpToDate', 'Supabase, OpenAI', 'doctor-in-the-loop') but directives like 'Trace the clinical claim path from source and retrieval through generation and UI rendering' and 'Verify conservative failure behavior' give no executable steps, commands, file paths, or checks. This is 'some concrete guidance but incomplete' (anchor 3) rather than anchor 4's 'mostly executable guidance', since the how for each check is left entirely implicit.

3 / 5

Workflow Clarity

The six items are listed and each states what to check ('Never introduce artificial keyword bans', 'Verify ... patient privacy'), but it is a policy checklist rather than a sequenced workflow: order carries no meaning, and validation checkpoints — what evidence to gather, which tests or files to inspect, or pass/fail criteria — are implicit. It matches anchor 3 ('steps listed but validation gaps ... checkpoints missing or implicit'), not anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no content that warrants external references, and the single '# Clinical' heading over a coherent six-item checklist is well-organized for its scale. Per the rubric's simple-skill guideline (under 50 lines, no need for external references), this earns a 5; there is no buried reference or inlined bulk that would place it at anchor 4.

5 / 5

Total

16

/

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 description that explicitly covers both what the skill does and when to use it, with a distinct product-anchored niche. Its main weakness is trigger-term naturalness: several trigger phrases are internal jargon and natural user synonyms are absent. It is also written in the required third person.

Suggestions

Add natural user-facing synonyms to the trigger clause, e.g. 'medical content', 'healthcare answers', or 'patient safety review', so it matches how a user would phrase the request.

Soften jargon-heavy trigger terms like 'ingestion' and 'source rendering' with plain-language equivalents alongside them.

DimensionReasoningScore

Specificity

Enumerates five concrete evidence domains — 'clinical safety, privacy, source-governance, rollback, and production-readiness' — plus the action 'Assemble ... evidence for PsychSift changes', listing several specific actions with only minor coverage gaps. It falls short of a 5 because the coverage relies on one assemble action rather than a comprehensive set of distinct concrete actions.

4 / 5

Completeness

Explicitly answers both questions: the 'what' is 'Assemble clinical safety, privacy, source-governance, rollback, and production-readiness evidence for PsychSift changes' and the 'when' is the explicit trigger clause 'Use for answer generation, retrieval, ingestion, clinical content, source rendering, or other patient-safety-sensitive behavior' with concrete trigger phrases. It clearly matches the anchor-5 example pattern and there is no higher level to drift to.

5 / 5

Trigger Term Quality

The trigger clause names six areas ('answer generation, retrieval, ingestion, clinical content, source rendering, or other patient-safety-sensitive behavior'), but several are developer jargon ('ingestion', 'source rendering', 'retrieval') rather than phrases users naturally say, and common synonyms like 'medical', 'healthcare', or 'patient safety review' are missing. This fits anchor 3 ('some relevant keywords but missing common variations or synonyms') better than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The description is anchored to a named product ('PsychSift') and a narrow clinical-safety niche, giving it a clear domain with distinct triggers ('clinical content', 'patient-safety-sensitive behavior') and minimal conflict risk with generic skills. It matches anchor 5 ('clear niche with distinct triggers') rather than anchor 4's 'minor overlap risk', since the product anchor alone disambiguates it.

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/clinical/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.