SKILLEMALL.ai

CC memory-sync-setup

Generates a project-tailored memory-sync skill: memory surface batches, checkable-fact catalogue, non-growth sync, independent verify, self-sync, agent re-audit. Triggers: memory sync init, generate memory sync, sync memory skill, установи memory-sync, синхронизируй память

kochetkov-ma/claude-brewcode Claude Code author: kochetkov-ma 11 files · 5 scripts body ≈ 10 154 tokens Open the sourcegithub.com↗ analyzed 32 h ago

Generates a project-tailored memory-sync skill: memory surface batches, checkable-fact catalogue, non-growth sync, independent verify, self-sync, agent…

As a process C 53/100 · Has gaps — References files that are not bundled: references/*.md, references/SKILL.md.template

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
81/100
safety, quality, tests
Safety 60%
95
Quality 40%
59
Run on models
none yet
Process rating
C
53/100
Has gaps
References files that are not bundled: references/*.md, references/SKILL.md.template
Tools and files w 18
0
Inputs and preconditions w 11
0
Result and completion w 14
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Edit Glob Grep Bash Agent AskUserQuestion

Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 10154 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: references/*.md
  • warning missing-ref reference to a missing file: references/SKILL.md.template
  • note edit-residue the text marks something as outdated (lines 88, 158, 321, 322, 452): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: references/*.md, references/SKILL.md.template
  • 0Tools and files. 2 referenced file(s) missing: references/*.md, references/SKILL.md.template
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 10154 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 40 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (16 tags): a typed call is more reliable

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)
  • +3Output format is not stated: the model decides each time
  • -212 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 273: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +3All 2 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.