BC encrypted docs
End-to-end encrypted .md documents for agents & humans to collaborate. This is a multiplayer alternative to gog and Google Docs that lets people (via CLI) and agents create, search and sync encrypted markdown docs. This service leverages https://ddocs.new which can be enabled locally or via your preferred cloud set-up to make docs accessible across any device or chatbot interface in complete privacy.
End-to-end encrypted .md documents for agents & humans to collaborate. This is a multiplayer alternative to gog and Google Docs that lets people (via CLI) and…
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlSKILL.md:75Webhook / callback URL commonly used for exfiltration (verify the destination) (security demo / example; quoted — discussed, not commanded)* Server URL: `https://<your-server-url>/` (e.g. `https://abc1…app/mcp`)
demoquoted -
low Exfiltration
exfil-webhook-urlSKILL.md:90Webhook / callback URL commonly used for exfiltration (verify the destination) (security demo / example; quoted — discussed, not commanded)* Server URL: `https://<your-server-url>/` (e.g. `https://abc1…app/`)
demoquoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 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. 19 mutating operations with no state check
- 40Consistency. Frontmatter name (encrypted docs) differs from the folder (encrypted-docs)
- 100Tools and files. No external tools needed
- 100Steps. 71 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 3072 tokens
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (3 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)
- +1No license
- +2Single-language instructions
- +3Description length 403: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 71 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.