SKILLEMALL.ai
RU Sign in

BF org-memory

Extends the org-cli skill so the agent also persists its own memory (knowledge, observations, daily notes) to an org workspace.

ClawHub Agent Skills author: DCPRevere v1.0.2 MIT-0 9 files body ≈ 1 205 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process F 32/100 · Will not run — References files that are not bundled: ../org-cli/SKILL.md

IntegrationAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
99
Quality 40%
65
Run on models
none yet
Process rating
F
32/100
Will not run
References files that are not bundled: ../org-cli/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

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 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
  • low Secrets in code secret-high-entropy-token plugin/package-lock.json:37
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…wQp+7C4n…9JQ==",
    detector

Files scanned: 9. 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 missing-ref reference to a missing file: ../org-cli/SKILL.md

Process rating: all ten parameters 32/100

Will not run. References files that are not bundled: ../org-cli/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../org-cli/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 85Steps. 5 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1205 tokens
  • 100Progress reporting. Reports progress

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
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 127: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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

External checks

ClawHub: suspicious
This memory skill is mostly purpose-aligned, but it needs review because it can persist and reload user-related notes across sessions and has weak file scoping for some write tools.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026