FF project-context-manager
Project-based agent context management system for maintaining long-term memory and project state across sessions. Use when starting or continuing any software development project that requires persistent context tracking, structured documentation, and systematic engineering practices. This skill enforces PROJECT_CONTEXT.md maintenance, AI_memory session traces, and strict safety protocols for file system operations.
As a process F 46/100 · Will not run — References files that are not bundled: references/workflow-examples.md, references/code-templates.md, references/safety-checklist.md
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
-
critical Dangerous commands
cmd-destructive-fsSKILL.md:262Destructive filesystem command (wipes root/home/drive)rm -rf /
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/workflow-examples.md - warning
missing-refreference to a missing file: references/code-templates.md - warning
missing-refreference to a missing file: references/safety-checklist.md
Process rating: all ten parameters 46/100
- 0Tools and files. 3 referenced file(s) missing: references/workflow-examples.md, references/code-templates.md, references/safety-checklist.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 52 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2818 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 419: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 52 items
- +3Output format is stated explicitly
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.