BF portfolio-manager
Comprehensive portfolio analysis using Alpaca MCP Server integration to fetch holdings and positions, then analyze asset allocation, risk metrics, individual stock positions, diversification, and generate rebalancing recommendations. Use when user requests portfolio review, position analysis, risk assessment, performance evaluation, or rebalancing suggestions for their brokerage account.
Comprehensive portfolio analysis using Alpaca MCP Server integration to fetch holdings and positions, then analyze asset allocation, risk metrics, individual…
As a process F 57/100 · Will not run — References files that are not bundled: references/alpaca_mcp_setup.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Dangerous commands
cmd-shell-rcreferences/alpaca-mcp-setup.md:76Writes to a shell startup fileecho 'export ALPACA_API_KEY="your_api_key_id"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcreferences/alpaca-mcp-setup.md:77Writes to a shell startup fileecho 'export ALPACA_SECRET_KEY="your_secret_key"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcreferences/alpaca-mcp-setup.md:78Writes to a shell startup fileecho 'export ALPACA_PAPER=true' >> ~/.bashrc
-
low Dangerous commands
cmd-shell-rcscripts/test_alpaca_connection.py:41Writes to a shell startup file (string literal in code, not executed; test fixture / example file)print(" echo 'export ALPACA_API_KEY=\"your_key\"' >> ~/.bashrc")code literalfixture -
low Dangerous commands
cmd-shell-rcscripts/test_alpaca_connection.py:42Writes to a shell startup file (string literal in code, not executed; test fixture / example file)print(" echo 'export ALPACA_SECRET_KEY=\"your_secret\"' >> ~/.bashrc")code literalfixture -
low Dangerous commands
cmd-shell-rcscripts/test_alpaca_connection.py:43Writes to a shell startup file (string literal in code, not executed; test fixture / example file)print(" echo 'export ALPACA_PAPER=\"true\"' >> ~/.bashrc")code literalfixture
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5586 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/alpaca_mcp_setup.md
Process rating: all ten parameters 57/100
- 0Tools and files. 1 referenced file(s) missing: references/alpaca_mcp_setup.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Steps. 219 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5586 tokens
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- low 11 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
- +4Description does not say when NOT to use the skill (false activations)
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 390: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 219 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.