write-spike
Use when starting a new initiative spike, investigating technical feasibility, assessing impact across services, or writing an engineering discovery document — produces a structured spike doc with diagrams and a private notes file
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow can ingest outsider-authored free text from runtime-fetched external documentation: Agent D “External Documentation” extracts URLs from the ticket description and fetches them (via CLI tools like `curl`), then the fetched page body becomes readable text in the LLM context.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The skill's Phase 1 "External Documentation" step explicitly extracts URLs from ticket descriptions and fetches them at runtime using CLI tools (gh, curl), then injects those fetched docs into the agent's context/instructions (e.g., external docs or markdown viewer links such as https://markdownviewer.pages.dev), so these runtime-fetched URLs can directly control prompts.
- Repository
- AndreJorgeLopes/proof-of-skill
- Commit
c92f3dc
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.