AA intelligence-desk-brief
Generate a portfolio-aware daily or on-demand risk analysis brief from public market data, company updates, earnings material, and macro context, then emit a host-consumable handoff for persistence. Every brief should open by restating the user's portfolio or watchlist and the industries or themes they care about, then explain what changed, which exposures matter, and what to make of it.
As a process A 82/100 · Runs to the end — weak spots: consistency, 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securityREADME.md:72Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- host-oriented Notion handoff payload generation
Files scanned: 37. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "requires" - note
frontmatter-keyunknown frontmatter key "config" - note
frontmatter-keyunknown frontmatter key "examples"
Process rating: all ten parameters 82/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (intelligence-desk-brief) differs from the folder (portfolio-risk-desk)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 74 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 1976 tokens
- low 10 top-level sections: this looks like several domains in one skill
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 390: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 74 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.