AB office-collaboration-radar-en
Extract an evidence-linked collaboration status card from chat logs, meeting notes, and project updates. Use when a user needs project progress, confirmed decisions, owner-and-deadline actions, blockers, cross-functional dependencies, human-review items, an executive summary, a radar chart, or stable JSON. Use this English package only when the user requests English output. It processes user-supplied local files, redacts common PII and credential patterns, and writes only to an explicit output path.
Extract an evidence-linked collaboration status card from chat logs, meeting notes, and project updates.
As a process B 69/100 · Nearly there — weak spots: failures and branches, running it twice, progress reporting
How to improve
- 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 Secrets in code
secret-labelled-tokenscripts/process.py:637Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)"api_key=sk-1…jkl Authorization: Bearer abcdefghijklmnop "
placeholder -
low Secrets in code
secret-password-literalscripts/process.py:637Hard-coded password / key literal (may be an example) (placeholder value)"api_key=sk-1…jkl Authorization: Bearer abcdefghijklmnop "
placeholder
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 26 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1318 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)
- +1No license
- +2Single-language instructions
- +3Description length 504: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.