Answer a design or feasibility question with explicitly throwaway spike code — never committed, findings recorded in the diary or an ADR draft. Use when a decision is blocked on "would X even work?" (library capability, API behavior, performance shape). Not for building features — that's /tdd via /implement.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The canonical home for this skill is prototype in agranado2k/google-books-clojure
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.
The spike workflow lets the agent install arbitrary dependencies from public package registries and probe third-party libraries, so it may read community-authored package docs or source at runtime, which is low-risk because the agent must select and fetch those packages itself.
agranado2k/tic-tac-toe-with-agentic-sdlc
931d5f3
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.