AC em-intel
Engineering Manager Intelligence: track team performance, engineer contributions, and project health across GitLab/GitHub + Jira/GitHub Issues. Use when asked for morning briefs, EOD reviews, team reports, quiet engineer alerts, epic health checks, or weekly newsletters. Maps engineer contributions to Jira tickets via feature branch analysis. Supports Slack, Telegram, and email delivery. Trigger on: /morning-brief, /eod-review, /team-report, "who worked on X", "which tickets are stalled", "send newsletter", "team performance".
As a process C 51/100 · Has gaps — weak spots: steps, inputs and preconditions, 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
exfil-webhook-urlcommands/setup_wizard.py:182Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)slack_webhook = _ask_secret(" Slack webhook URL (https://hooks.slack.com/...)")placeholder -
low Exfiltration
exfil-webhook-urlcore/delivery.py:50Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)f"https://api.telegram.org/bot{token}/sendMessage",vendor-hostquoted -
low Exfiltration
exfil-webhook-urlSETUP.md:87Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)SLACK_WEBHOOK_URL=https://hooks.slack.com/services/T.../B.../xxx
placeholder -
low Exfiltration
read-dotenvSKILL.md:53Reads a .env filecp .env.example .env
Files scanned: 25. 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 51/100
- 0Steps. Prose only: no discrete steps
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 882 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 532: enough signal without eating the budget
- +4Structure: 7 headings
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.