CtrlK
BlogDocsLog inGet started
Tessl Logo

status

Display the current state of the FPF knowledge base

51

Quality

55%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/fpf/skills/status/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid status-check skill with clear, actionable instructions and well-defined workflow steps. Its main weakness is moderate redundancy between the status report format template and the example output section, which inflates token usage without adding proportional value. The phase detection logic and evidence freshness classification are well-structured decision aids.

Suggestions

Remove or significantly trim the 'Example Output' section since the 'Status Report Format' already provides a complete template—having both is redundant.

Consider removing the date '2025-01-15' from the Recent Decisions example to avoid time-sensitive content, or mark it clearly as illustrative.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy—the full status report format and the example output overlap significantly, showing essentially the same information twice. The phase detection table and evidence freshness logic are useful but could be slightly tighter.

2 / 3

Actionability

The skill provides concrete, specific guidance: exact directory paths to check, a clear output format template, a precise phase detection table with conditions and next steps, and explicit evidence freshness classification rules with date comparisons. Everything is directly executable.

3 / 3

Workflow Clarity

The 5-step action sequence is clearly numbered and unambiguous. The phase detection logic table serves as an effective decision tree with explicit next steps. Evidence freshness checking includes a clear classify-then-warn flow. For a status/reporting skill, this level of workflow clarity is excellent.

3 / 3

Progressive Disclosure

The content is well-structured with clear sections, but it's somewhat long for a single file with no bundle support. The detailed status report format, phase detection logic, evidence freshness rules, and example output could benefit from being split or the example output could be removed since the format template already covers it.

2 / 3

Total

10

/

12

Passed

Description

32%

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 is too terse and lacks explicit trigger guidance ('Use when...'), which significantly limits Claude's ability to know when to select this skill. While 'FPF knowledge base' provides some domain specificity, the description fails to explain what FPF is, what 'current state' means concretely, or under what circumstances this skill should be invoked.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to see, view, or check the status of the FPF knowledge base.'

Include natural trigger terms users might say, such as 'show', 'list', 'view', 'status', 'knowledge base contents'.

Expand on what 'display the current state' means concretely—e.g., 'Lists all entries, categories, and metadata in the FPF knowledge base.'

DimensionReasoningScore

Specificity

It names a specific domain ('FPF knowledge base') and one action ('display the current state'), but does not list multiple concrete actions or elaborate on what 'display' entails.

2 / 3

Completeness

It partially answers 'what does this do' but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

Includes 'FPF knowledge base' and 'current state' which are somewhat relevant keywords, but 'FPF' is jargon without explanation, and common user variations (e.g., 'show', 'list', 'status', 'view') are missing.

2 / 3

Distinctiveness Conflict Risk

'FPF knowledge base' is a fairly specific domain reference that reduces conflict risk, but the action 'display the current state' is generic enough that it could overlap with other status/display skills.

2 / 3

Total

7

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
NeoLabHQ/context-engineering-kit
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.