agentleFS
Sign inStart free
metaspartanmetaspartan/cybara/skills/spike/SKILL.md

spike

Skill38 starsChanged 5 months agoMITView on GitHub

Run a throwaway spike/prototype to validate feasibility or compare approaches, then report a clear verdict. Use when the user is unsure an approach works and wants a quick proof before committing.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-news-monitor, blocked-page-recovery and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aivrarSkill

    competitor-news-monitor

    Watch named companies for material news; cited digests.

    Also in 6 projects that use this

  • aivrarSkill

    blocked-page-recovery

    Recover blocked/paywalled/WAF'd pages via fallbacks.

    Also in 6 projects that use this

  • john-data-chenSkill

    teams-meeting-pipeline

    Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

    Also in 8 projects that use this

  • john-data-chenSkill

    touchdesigner-mcp

    Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

    Also in 5 projects that use this

  • Tommy-ywSkill

    songwriting-and-ai-music

    Songwriting craft, AI music generation prompts (Suno focus), parody/adaptation techniques, phonetic tricks, and lessons learned. These are tools and ideas, not rules. Break any of them when the art calls for it.

    Also in 8 projects that use this

  • mae616Skill

    p5js

    p5.js（クリエイティブコーディング）のProcessing由来「コードでスケッチ」思想を軸に、setup/drawループ・座標系・インタラクション・パフォーマンス最適化を整理する。p5.js、Processing、クリエイティブコーディング、ジェネラティブアート、インタラクティブ表現、ビジュアルプログラミング、Canvas描画、パーティクル、フラクタル、ノイズ表現に関する相談で必ず使うこと。ユーザーが「コードでアート」「動くビジュアル」「インタラクティブな描画」と言った場合にも適用する。

    Also in 8 projects that use this

  • +4 more from aivrar

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Measure the actual thing: Run it; capture timing/output/errors.

    line 21
  2. Distinctive:

    Keep spikes honest: a "no, this won't work" verdict with evidence is a successful spike.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spike

A spike is a time-boxed, throwaway investigation. Its output is a decision, not production code.

When to use

  • "Will approach X even work?" / "Can we do Y with Z?"
  • Comparing 2+ approaches and needing empirical data, not opinion.
  • De-risking an unknown (an API, a library, a perf claim) before building the real thing.

Procedure

  1. State the question precisely. What must be true for the approach to be viable? ("Can library X parse a 1GB file in <2s without OOM?")
  2. Set a time/effort box. Spikes are short — if it's taking long, narrow the question.
  3. Write the minimum code to answer the question. Use exec/write in an isolated scratch path (e.g. spike/). Don't worry about quality.
  4. Measure the actual thing. Run it; capture timing/output/errors. Don't extrapolate.
  5. Report a verdict:
    • Verdict: VIABLE / NOT VIABLE / NEEDS-MORE-INFO
    • Evidence: concrete numbers, snippet, or the failure mode observed.
    • Recommendation: proceed with X / avoid X because / next probe needed.
  6. Clean up the scratch code (or move it aside) unless it's promoted to real code.

Anti-patterns

  • Spending a spike polishing code instead of answering the question.
  • Reporting "it should work" without measuring.
  • Letting a spike silently become production code without a review pass.

Keep spikes honest: a "no, this won't work" verdict with evidence is a successful spike.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free