CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ingest

Triage and verify PsychSift document ingestion, extraction, queueing, retries, workers, batches, and failure recovery. Use for uploads, ingestion jobs, extraction defects, worker reliability, or queue behavior.

Quality

84%

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

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.

The body is exceptionally concise and appropriately scoped for a short procedural skill, with a coherent six-step sequence and safety gating. Its weakness is actionability: it reads as a checklist of what to consider rather than how to execute, with no concrete commands, paths, or explicit validation loops.

Suggestions

Add at least one concrete executable anchor per phase, e.g. the actual command to run the ingestion test suite, the fixture directory path, or the script used to inspect local queue state, so "Reproduce with fixtures, unit tests, or mocked/local queue state" becomes directly actionable.

Insert an explicit validation checkpoint with a feedback loop, e.g. "Verify the reproduction fails/pass exactly as reported; if not, re-map the stage before proceeding" — currently checkpoints like "before considering live services" are only implicit.

Name the key repo entry points (upload handler, worker code, queue schema) in step 1 so "Map the local path" points at real files instead of requiring discovery from scratch.

DimensionReasoningScore

Conciseness

Six lean numbered lines with zero padding, no explanation of concepts Claude already knows, and every token carrying load (e.g., "Check idempotency, retry limits, partial failure, cancellation, owner scope, file safety, and observability") — fully matching the lean-and-efficient anchor.

5 / 5

Actionability

It names concrete concerns ("idempotency, retry limits, partial failure, cancellation, owner scope") and specific technologies ("Supabase functions", "live buckets"), but offers no commands, file paths, test names, or executable steps — "Map the local path" and "Reproduce with fixtures" are high-level hints with key details missing, fitting anchor 3 rather than the executable anchor 4.

3 / 5

Workflow Clarity

A clear sequence exists (map → reproduce → check concerns → run smallest test → gate approvals → report), but checkpoints are implicit ("before considering live services") rather than explicit validation steps, and a batch/queue ingestion workflow lacks any validate→fix→retry feedback loop, capping it at anchor 3 per the batch-operations rule.

3 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no external files needed, and well-organized as a single headed numbered list — the simple-skill exception applies and the content is clear and easy to navigate.

5 / 5

Total

16

/

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, with an explicit Use-for trigger clause covering five concrete scenarios and a specific, product-scoped capability list. The only weakness is that trigger coverage omits a few natural synonyms (imports, failed jobs).

DimensionReasoningScore

Specificity

"Triage and verify" covers seven named pipeline stages ("ingestion, extraction, queueing, retries, workers, batches, and failure recovery"), listing several specific capabilities with minor gaps — it never says what action is taken for each stage, so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers "what" ("Triage and verify PsychSift document ingestion, extraction, queueing, retries, workers, batches, and failure recovery") and "when" with concrete trigger phrases ("Use for uploads, ingestion jobs, extraction defects, worker reliability, or queue behavior"), mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

"Use for uploads, ingestion jobs, extraction defects, worker reliability, or queue behavior" gives good natural keyword coverage a user would actually say, but misses common variations like "imports", "failed jobs", or "stuck/stalled queue" — matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Scoping to the named product "PsychSift" with system-specific triggers (ingestion jobs, worker reliability, queue behavior) creates a clear niche with minimal conflict risk against generic document or file skills.

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