CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rag-cloud-sdd

Execute one RAG Cloud phase with fresh agents, adaptive effort, immutable review ranges, and fail-closed routing.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/rag-cloud-sdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 an extremely token-efficient, well-sequenced checklist with explicit stop conditions and a review feedback loop, but its guidance is more directive than executable — nearly every step presupposes unstated commands or external context, and its one script reference points to a file that is not in the bundle. Workflow structure is solid; actionability and reference organization are the weak points.

Suggestions

Provide the exact invocation for the launch check (e.g. `node scripts/rag-phase-launch-check.mjs --phase <TARGET_PHASE> --effort <level>`) and concrete commands for hashing and route verification instead of naming them abstractly.

Expand compressed directives like "bind the manifest-routed fresh read-only probe's source/receipt inspection and dispatch metadata" into concrete sub-steps or move the detail into a bundled reference file with a clear pointer.

Either bundle the referenced `scripts/rag-phase-launch-check.mjs` (and any phase-skill references) or restructure the body so each external dependency is clearly signaled with its path and purpose.

DimensionReasoningScore

Conciseness

The body is maximally terse with zero padding and no explanations of concepts Claude already knows — e.g. "Record `TASK_BASE`; generate the brief; dispatch one fresh implementer" carries only instructions. Every token is instructional and assumes competence, matching anchor 5; nothing can be trimmed without losing information.

5 / 5

Actionability

Only one concrete artifact is named ("Run `scripts/rag-phase-launch-check.mjs` with target/effort") and even that lacks invocation syntax; the rest — "Require authoritative route evidence. Hash controller/helpers/phase skills; bind the manifest-routed fresh read-only probe's source/receipt inspection" — are high-level directives missing the specific commands or steps to execute. This matches anchor 2 (minimal concrete guidance) rather than 3, since no executable command sequence or code exists anywhere in the body.

2 / 5

Workflow Clarity

Steps 1-7 form a clear ordered sequence with explicit checkpoints and stop conditions ("Stop on unverified routes/capabilities", "Validate; push only when authorised; stop") plus a feedback loop in step 6 (return findings, then "re-review the full range"), matching anchor 4. Not 5, because the compressed phrasing leaves how to perform several checkpoints (hashing, route binding) ambiguous in execution.

4 / 5

Progressive Disclosure

The body references `scripts/rag-phase-launch-check.mjs` but no scripts/ directory exists in the bundle, and it defers heavily to external context ("Read `AGENTS.md`") without clearly signaling where detail lives; the dense per-phase procedure is inlined rather than split into references. This matches anchor 3 (some structure, references not clearly resolvable, content that should be separate is inline); not lower because the body itself is short and organized.

3 / 5

Total

14

/

20

Passed

Description

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

The description states a single concrete action within a distinctive niche, but it omits any 'when to use' guidance and leans on internal jargon ("immutable review ranges", "fail-closed routing") that does not communicate capabilities to a reader outside the project. It is a mid-range description: distinctive but incomplete and light on natural trigger terms.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g. 'Use when asked to execute or run a RAG Cloud phase, or to continue the RAG Cloud SDD workflow').

Replace or unpack internal jargon like 'adaptive effort, immutable review ranges, and fail-closed routing' with plain-language capability statements a user would recognize.

Include natural keyword variations users might say, such as 'RAG Cloud', 'phase execution', or specific phase names.

DimensionReasoningScore

Specificity

"Execute one RAG Cloud phase" is a single concrete action, but the remaining phrases ("adaptive effort, immutable review ranges, fail-closed routing") are process attributes and internal jargon rather than additional concrete actions. This matches anchor 3 (domain plus 1-2 concrete actions), not 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is stated ("Execute one RAG Cloud phase with fresh agents..."), but the 'when' is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4, because anchor 4 requires both 'what' and 'when'.

3 / 5

Trigger Term Quality

"RAG Cloud phase" is a meaningful domain keyword a user in this project could say, but the description offers no synonyms, variations, or explicit trigger phrasing. It sits above anchor 2 (generic keywords like "works with files") but below anchor 4 (good natural-term coverage) because no "Use when"-style trigger terms exist.

3 / 5

Distinctiveness Conflict Risk

"RAG Cloud phase" names a clear niche that is unlikely to trigger unrelated skills, giving only minor overlap risk — matching anchor 4. Not 5, because the top anchor expects clearly distinct trigger phrasing, which the description lacks.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/rag-phase-launch-check.mjs)

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.agents/skills/rag-cloud-sdd/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.