CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

status

Display the current state of the FPF knowledge base

Quality

72%

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 ./plugins/fpf/skills/status/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 content is a lean, well-structured status-check skill with concrete paths, thresholds, and phase-detection logic and no unnecessary concept explanations. Its only real weakness is mild duplication between the status report format template and the example output, and the absence of explicit validate-fix feedback loops.

DimensionReasoningScore

Conciseness

The body is well-organized with tables and numbered steps and assumes Claude's competence (no concept explanations), though the full status report format template plus a separate example output introduces some mild duplication that could be trimmed.

4 / 5

Actionability

Concrete, executable guidance is provided — exact directory paths, frontmatter field to read (valid_until), explicit freshness thresholds (> today + 30 days), and a phase-detection table — with only minor gaps such as no concrete command for listing/counting files.

4 / 5

Workflow Clarity

The five-step Action sequence is clear with explicit phase-detection and evidence-classification logic, and it warns the user on stale/expired evidence; it stops short of explicit validate-then-fix feedback loops, hence 4 rather than 5.

4 / 5

Progressive Disclosure

A self-contained skill with no bundle files and well-organized sections covering structure, format, phase logic, and an example; per the rubric a sub-50-line single-purpose skill with no need for external references can score 5 with well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

51%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 clearly states a single concrete action on a distinct domain but omits any 'Use when...' trigger guidance and does not enumerate multiple capabilities or natural user phrasings. It is a competent-but-thin description capped by the missing trigger clause.

Suggestions

Add a 'Use when...' clause spelling out natural triggers, e.g. 'Use when the user asks for FPF status, wants to check the knowledge base state, or needs to see hypothesis/evidence/decision counts.'

List 2-3 specific capabilities (counts by layer, evidence freshness check, phase detection) so the description conveys more than one action.

Include synonyms/file references users might actually say (e.g. 'FPF status', 'knowledge base state') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Display the current state of the FPF knowledge base" names the domain (FPF knowledge base) and one concrete action (display state), but offers only a single generic action rather than a list of specific capabilities.

3 / 5

Completeness

The description gives a clear 'what' (display current state) but no explicit 'when to use it' guidance; per the rubric a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"FPF knowledge base" and "state"/"status" are relevant but there is no 'Use when...' clause and natural user phrasings or synonyms (e.g., 'FPF status', 'check knowledge base') are not enumerated.

3 / 5

Distinctiveness Conflict Risk

"FPF knowledge base" is a fairly distinct niche tied to a specific framework, with only minor overlap risk against other FPF-related skills; it lacks the explicit triggers that would push it to 5.

4 / 5

Total

13

/

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

NeoLabHQ/context-engineering-kit

Path

plugins/fpf/skills/status/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.