BF employee-reminder-ops
Google Sheets-driven employee reminder and special-event reporting workflow for internal operations. Use when setting up or migrating birthday reminders, daily management reports, Telegram/Discord reminder routing, Google Sheets staff/event schemas, or scheduled reporting jobs that read Sheets and send summaries into team chats.
As a process F 33/100 · Will not run — References files that are not bundled: assets/windows/
How to improve
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenreferences/PLAN_A_DEMO_USAGE.md:38High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Sheet ID: `17JU…nn8`
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/plan-a-demo.js:8High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)spreadsheetId: process.env.PLAN_A_SHEET_ID || '17JU…nn8',
quoted -
low Exfiltration
read-dotenvscripts/run-plan-a.sh:5Reads a .env filesource ./.env.plan-a
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/windows/
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: assets/windows/
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 501 tokens
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
- +4No input/output examples
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 330: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 45 items
- +4Reference files are cited in the instructions (7 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.