CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

source-governance

Audit PsychSift source metadata, citations, approvals, labels, provenance, rendering, and release-governance coverage. Use for citation defects, source-governance changes, document labels, public promotion, or clinical evidence traceability.

Quality

86%

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.

An exceptionally lean, well-sequenced audit checklist that respects the token budget and gates risky operations behind approval. Its weakness is actionability: it consistently says what to check but never how — no script paths, test invocations, or expected signals.

Suggestions

Name the concrete verification commands or script entry points (e.g., the actual governance script and an example test/fixture invocation) so step 3's 'focused local tests and fixture checks' is executable rather than aspirational.

For step 5, state what 'conservative behavior' looks like for each degraded source state (e.g., expected fallback citation text or suppression rule), so verification has a pass/fail signal.

Add a short feedback loop for step 2 — what to do when a metadata check fails (fix, re-run, or escalate to the approval-required bucket) — to lift workflow clarity to the next anchor.

DimensionReasoningScore

Conciseness

Six terse numbered directives (~120 words) with zero padding and no explanation of concepts Claude already knows — "Trace source identity from ingestion metadata through retrieval, answer citations, and UI rendering" carries maximal information per token.

5 / 5

Actionability

The guidance names concrete systems ("scripts that query live Supabase"), states edge conditions ("absent, stale, private, rejected, or ambiguous"), and mandates "focused local tests and fixture checks" — but never specifies which scripts, test commands, fixture locations, or expected outcomes, leaving the how-to executable details missing per the anchor-3 definition.

3 / 5

Workflow Clarity

The sequence trace → check metadata → local tests first → approval-gate live data → verify conservative behavior → report is clearly ordered, with checkpoints in steps 3 and 5, but there is no explicit feedback loop describing what to do when a check fails, keeping it below anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no bundle files, and needs no external references — the single heading with a flat numbered list is appropriately organized for a skill of this size, per the simple-skill guideline.

5 / 5

Total

17

/

20

Passed

Description

87%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, and explicit about both capabilities and trigger conditions, with domain-specific triggers that make misfiring unlikely. The only soft spot is that capability coverage hangs on one verb and trigger terms lack synonyms or variations.

DimensionReasoningScore

Specificity

Enumerates several concrete audit targets — "source metadata, citations, approvals, labels, provenance, rendering, and release-governance coverage" — with comprehensive domain coverage, but rests on a single verb ("Audit") rather than multiple distinct actions, so it falls just short of the anchor-5 example.

4 / 5

Completeness

Clearly answers both: "Audit PsychSift source metadata, citations, approvals, labels, provenance, rendering, and release-governance coverage" states the what, and an explicit "Use for ..." clause with concrete trigger phrases states the when — matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

"Use for citation defects, source-governance changes, document labels, public promotion, or clinical evidence traceability" gives good natural-phrase coverage a PsychSift user would plausibly say, though synonyms and common variations are missing.

4 / 5

Distinctiveness Conflict Risk

The "PsychSift" / "source-governance" niche with domain-unique triggers like "citation defects" and "clinical evidence traceability" is clearly distinguishable from any generic skill, giving minimal conflict risk.

5 / 5

Total

18

/

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/source-governance/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.