CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

database-flightplan

Compatibility alias for the plan skill. Use only when the user explicitly invokes the older database-flightplan name; otherwise use plan for risk-scoped offline verification planning.

Quality

90%

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

100%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 a near-ideal compatibility alias: three lean, unambiguous steps that delegate to the canonical skill, forbid duplication, and correct the naming going forward. The only inherent limitation — the external path cannot be verified from this bundle — is a property of alias skills rather than a structural flaw in the content.

DimensionReasoningScore

Conciseness

The body is three terse numbered lines with zero padding or explanation of concepts Claude already knows; every token earns its place, matching the 'lean and efficient' top anchor.

5 / 5

Actionability

The guidance is fully executable for an instruction-only skill: an exact file path to read and follow ('.agents/skills/plan/SKILL.md') plus a concrete naming directive ('Use `plan` in recommendations and new documentation'). Per the scoring notes, absence of code is not penalized when the guidance is this specific.

5 / 5

Workflow Clarity

The simple-skill exception applies: this is a single-task alias whose one action (read and follow the plan skill) is unambiguous, and the three numbered steps are clearly sequenced. No destructive or batch operations exist, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with a single, clearly signaled, one-level-deep reference to the canonical skill's SKILL.md and no nested reference chains, which is the ideal structure for an alias. No bundle files exist, which is appropriate here; the referenced path points to a sibling skill in the source project and could not be verified within this bundle, but the written structure is exemplary.

5 / 5

Total

20

/

20

Passed

Description

75%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 well-crafted alias description: it states exactly what the skill is, gives an explicit and narrow trigger condition, and actively routes general planning requests to the canonical plan skill. Keyword coverage and action specificity are adequate rather than comprehensive, since natural name variations are omitted.

Suggestions

Mention the standalone natural variation 'flightplan' (e.g., 'when the user invokes database-flightplan or flightplan') so users typing the short name still route correctly.

Add one concrete phrase about what the underlying plan skill actually does (e.g., 'offline verification planning with risk scoring') to slightly raise action specificity without adding padding.

DimensionReasoningScore

Specificity

The description names the domain ("risk-scoped offline verification planning") and 1-2 concrete behaviors ("Compatibility alias for the plan skill", routing on legacy invocation), matching the anchor for domain plus 1-2 concrete actions. It does not list several specific actions, so anchor 4 is not reached.

3 / 5

Completeness

It explicitly answers both what ("Compatibility alias for the plan skill") and when ("Use only when the user explicitly invokes the older database-flightplan name; otherwise use plan") with a concrete trigger phrase, matching the top anchor. An explicit 'Use when' clause is present, so no cap applies.

5 / 5

Trigger Term Quality

Relevant keywords are present ("database-flightplan", "plan", "verification planning"), but common natural variations a user might say are missing ("flightplan" standalone, "flight plan", "PsychSift"), matching the 'some relevant keywords but missing common variations' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (explicit legacy-name invocation only) and actively disambiguates against the sibling plan skill ("otherwise use plan"), yielding minimal conflict risk. It is not merely 'mostly distinct' as in anchor 4 because the routing boundary is fully explicit.

5 / 5

Total

16

/

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/database-flightplan/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.