BD inbox-to-action-closer
Orchestration skill that processes raw work-item data from Slack, GitHub, calendar, Notion, Trello, and email — supplied by the caller or by other OpenClaw tools — and produces a single merged, prioritised action board with owners, due dates, reply drafts, and follow-up questions. Does not connect to external APIs directly; it normalises, deduplicates, scores, and renders data that is provided to it.
As a process D 49/100 · Unfinished process — 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:20High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…yi2+Iq5p…IcQ/Uiv9…umq/5nqz…9NA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:245High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:273High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…pm5+2ww5uIE6lkO/6jcO…bdW+kBA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:332High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…6Ao+2AeY…EPK+We3n…cgW/DoA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:342High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…YdL+SDH7dVM8gjy+ERp3…FJE+02ka…nXg==",
detector
Files scanned: 28. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/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. 3 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 788 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 403: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 22 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.