CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api

Review PsychSift route and function contracts for validation, authentication, authorization, errors, retries, idempotency, compatibility, and safe provider boundaries. Use for API route, edge function, webhook, or public contract work.

Quality

91%

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.

The body is an exemplarily lean six-step review checklist with a clear sequence and verification checkpoints, appropriately sized for a skill with no bundle files. Its only weakness is the absence of concrete examples (e.g., a canonical error envelope or a sample route-unit test invocation) that would make the guidance fully executable.

DimensionReasoningScore

Conciseness

Six terse imperative steps with zero padding and no explanation of concepts Claude already knows — every token earns its place. Matches the "lean and efficient; assumes Claude's competence" anchor exactly.

5 / 5

Actionability

The checklist is directive and specific ("Test invalid, empty, oversized, duplicate, stale, unauthorized, timeout, retry, and dependency-failure cases"; "Use route-unit tests and mocks locally"), but provides no concrete examples such as an error-envelope shape or a sample test command. Above score 3 (guidance is complete and specific, not vague or pseudocode) but below score 5 (not copy-paste ready), and code absence is not penalized for an instruction-only skill.

4 / 5

Workflow Clarity

A clear six-step sequence (identify → test → check → local verification → secrets check → report) with checkpoints like "Verify secrets and privileged clients remain server-only" and "Report... focused proofs, and untested live integrations". Below score 5 because there is no explicit fix-and-retry feedback loop; above score 3 because checkpoints are present, and the skill is not destructive or batch so the cap of 3 does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist), and the numbered-list structure is well-organized with no content that should be split out. Per the simple-skill guideline, this earns a 5.

5 / 5

Total

18

/

20

Passed

Description

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

This is a strong description: it states concrete capabilities comprehensively, includes an explicit third-person 'Use for...' trigger clause with natural keywords, and is tightly scoped to a distinct niche. The only gap is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

"Review PsychSift route and function contracts for validation, authentication, authorization, errors, retries, idempotency, compatibility, and safe provider boundaries" lists eight specific concrete review actions with comprehensive coverage of the API contract review domain. It exceeds the score-4 anchor ("minor gaps in coverage") because no meaningful review dimension is missing.

5 / 5

Completeness

Both questions are explicitly answered: the what ("Review PsychSift route and function contracts for validation, authentication, authorization, errors, retries, idempotency...") and the when ("Use for API route, edge function, webhook, or public contract work") with concrete trigger phrases. Matches the score-5 anchor exactly; score 4 would require the when clause to be less explicit than it is.

5 / 5

Trigger Term Quality

"Use for API route, edge function, webhook, or public contract work" provides good natural keyword coverage, but common variations like "endpoint", "REST", or "handler" are absent. It is above score 3 (terms are natural and domain-relevant, not generic) but below score 5 (no synonym-level coverage).

4 / 5

Distinctiveness Conflict Risk

The project-scoped "PsychSift" naming combined with distinct trigger surfaces ("API route, edge function, webhook, or public contract work") gives a clear niche with minimal conflict risk. Overlap with a generic code-review skill is possible but the contract-focused triggers are distinct.

5 / 5

Total

19

/

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