CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reset

Reset the FPF reasoning cycle to start fresh

Quality

65%

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 ./antigravity/skills/reset/SKILL.md

The canonical home for this skill is reset in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, largely executable instruction skill: three reset variants each backed by concrete bash commands and a complete session-archive template, with no wasted explanation. Its main weakness is validation around destructive operations — the hard reset permanently deletes all FPF data with only a warning and no confirmation or post-check, which caps workflow clarity. Adding verification steps (confirm intent, verify the archive, check directories are empty) would raise it substantially.

Suggestions

Add an explicit validation checkpoint before the Hard Reset — e.g., confirm the user's intent in plain words and verify the session archive was written before running any rm -rf — since destructive deletion without validation caps workflow clarity at 3.

Add a post-move verification step (e.g., "ls .fpf/knowledge/L0/" to confirm the directories are empty) rather than silently suppressing errors with "2>/dev/null || true", so a failed move is detected instead of hidden.

Tell Claude how to gather the "State at Reset" hypothesis counts for the archive (e.g., count files under .fpf/knowledge/L0..L2 and invalid/) so the archive and the completion report reflect verified state rather than hardcoded example values.

DimensionReasoningScore

Conciseness

The body is command-first and assumes competence — no explanations of concepts Claude already knows — with only minor trimmable redundancy: the opening line "Reset the FPF reasoning cycle to start fresh." restates the description verbatim, and the session-archive template runs ~30 lines. Not score 5 because of that restatement and template padding; not score 3 because nothing teaches known concepts or pads beyond the template.

4 / 5

Actionability

Concrete, executable bash for every option ("mkdir -p .fpf/archive/session-2025-01-15", "mv .fpf/knowledge/L0/*.md ... 2>/dev/null || true", "rm -rf .fpf/knowledge/L0/*.md") plus a copy-paste markdown template. Minor gaps keep it from 5: the template hardcodes example dates and hypothesis counts, and there is no instruction for how to gather the "State at Reset" counts (e.g., listing files in the knowledge directories) before writing the archive.

4 / 5

Workflow Clarity

Option 1 is a clear numbered sequence (create archive → move → report) and the three options are well-labeled, but the destructive Hard Reset runs "rm -rf .fpf/knowledge/L0/*.md" (and five more like it) with only a WARNING and no validation checkpoint — no user-confirmation step, no check that the archive exists before deleting. Per the rubric's cap, a destructive skill without validation cannot score above 3. Not score 2 because steps are concrete and coherently sequenced.

3 / 5

Progressive Disclosure

Good structure: "## Action (Run-Time)" with three clearly signaled "### Option" sections, numbered sub-steps, and no nested or buried references (the skill has no bundle files). It misses 5 because at ~106 lines it exceeds the simple-skill threshold and the 30-line session-archive example is inlined where a reference file could carry it; not 3 because organization is genuinely clear and nothing is misplaced.

4 / 5

Total

15

/

20

Passed

Description

45%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 is clear about what the skill does but stops there: it is a single generic action on a named domain with no "Use when..." trigger guidance and no enumeration of the reset variants (soft archive, hard delete, decision reset). It reads as a bare restatement of the skill name. Adding explicit triggers and the concrete reset options would lift specificity, completeness, and distinctiveness together.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to reset, clear, or start fresh with the FPF reasoning cycle, or wants to archive or wipe the current session" — the missing 'when' currently caps completeness at 3.

Enumerate the concrete reset variants in the description (archive current session, hard-delete all FPF data, re-evaluate existing hypotheses) so it lists specific actions rather than one generic "reset" verb.

Include natural trigger synonyms such as "clear", "wipe", "restart", and "new session" to broaden keyword coverage for users who won't say "reset".

DimensionReasoningScore

Specificity

"Reset the FPF reasoning cycle to start fresh" names the domain (FPF reasoning cycle) but offers only a single generic action — "reset" with "start fresh" restating the same intent — matching the one-action-plus-domain pattern of "Processes PDF files". It is not score 3 because there are no 1-2 distinct concrete actions listed (e.g., archive session, delete data, re-evaluate hypotheses), and not score 1 because the domain is named rather than pure abstraction.

2 / 5

Completeness

It has a clear "what" ("Reset the FPF reasoning cycle") but no "when" clause at all — no "Use when..." or equivalent trigger guidance, which per the guidelines caps completeness at 3. Not score 4 because the "when" is entirely absent rather than merely imprecise; not score 2 because the "what" is clear, not vague.

3 / 5

Trigger Term Quality

"reset" and "start fresh" are natural phrases a user of this system would say, plus the domain term "FPF reasoning cycle". However coverage is thin with no common variations or synonyms ("clear", "wipe", "restart", "new session"), matching anchor 3 rather than 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

The "FPF reasoning cycle" qualifier gives it a specific niche, but the generic verbs "reset" / "start fresh" without trigger scoping leave moderate overlap risk with sibling FPF lifecycle skills and any generic reset/fresh-start skill. It sits between anchor 3 ("could still overlap with similar skills") and anchor 4, but the missing trigger guidance keeps it at 3.

3 / 5

Total

11

/

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

antigravity/skills/reset/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.