agentleFS
friuns2friuns2/openclaw-android-assistant/skills/spike/SKILL.md

spike

Skill573 starsChanged 39 days agoMITView on GitHub

Run throwaway prototypes to validate feasibility, compare approaches, and report a verdict.

56 other projects use a version of this, 1 of them edited.

How people change it

All 1 edited versions we compared keep every one of its 9 rules.

Of the 1 edited version we compared: 1 keep every rule.

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

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.
  • Samin12Skill

    competitor-news-monitor

    Watch named companies for material news; cited digests.

    Also in 6 projects that use this

  • nobodyohm-webSkill

    blocked-page-recovery

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

    Also in 6 projects that use this

  • Samin12Skill

    document-to-action-items

    Extract cited obligations, deadlines, tasks from documents.

    Also in 6 projects that use this

  • michaellam26Skill

    sdlc-review

    Trigger stage-specific reviews for an SDLC project and save results to reviews/

    Also in 5 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

  • 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

  • +1 more from Samin12

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 8

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use when the user wants to test an idea before committing to a real build: "spike this", "quick prototype", "is this possible", "compare …

    line 9
  2. Distinctive:

    Do not use when reading docs/code can answer the question, or when the user clearly asked for production implementation.

    line 11
  3. Very specific:

    Default workspace: .tmp/openclaw-spikes/<slug> unless user asks for a tracked repo-local path.

    line 23
  4. Distinctive:

    Prefer runnable CLI, tiny HTML, one endpoint, or focused test.

    line 25
  5. Distinctive:

    Avoid package sprawl, Docker, env files, app frameworks, and production cleanup.

    line 26
  6. Distinctive:

    Run the riskiest question first.

    line 31
  7. Distinctive:

    Ask before building all variants if the work is more than a small prototype.

    line 33
  8. Distinctive:

    Do not merge spike code into production without rewriting it normally.

    line 50
  9. Distinctive:

    If external dependencies are evaluated, check health: recent release/commit, docs, license, install friction.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 43 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

Use when the user wants to test an idea before committing to a real build: "spike this", "quick prototype", "is this possible", "compare A/B", "before we build".

Do not use when reading docs/code can answer the question, or when the user clearly asked for production implementation.

Loop

  1. Question: state the concrete feasibility question.
  2. Research: read enough docs/source to choose credible approach.
  3. Build: create the smallest runnable artifact that validates or invalidates the idea.
  4. Stress: try one edge case or failure mode.
  5. Verdict: VALIDATED, PARTIAL, or INVALIDATED.

Output shape

  • Default workspace: .tmp/openclaw-spikes/<slug> unless user asks for a tracked repo-local path.
  • Repo-local option: spikes/<NNN-slug>/ with README.md and minimal code.
  • Prefer runnable CLI, tiny HTML, one endpoint, or focused test.
  • Avoid package sprawl, Docker, env files, app frameworks, and production cleanup.

Multi-spike ideas

  • Split into 2-5 independent questions.
  • Run the riskiest question first.
  • For A/B comparisons, keep inputs equal and measure the same dimensions.
  • Ask before building all variants if the work is more than a small prototype.

Verdict format

## Verdict: VALIDATED | PARTIAL | INVALIDATED

Question: ...
Evidence: exact command/output/measurement.
What worked: ...
What failed or surprised us: ...
Recommendation: ship / adjust / avoid, with the next production step.

Rules

  • An invalidated spike is useful when it rules out a path with evidence.
  • Do not merge spike code into production without rewriting it normally.
  • If external dependencies are evaluated, check health: recent release/commit, docs, license, install friction.

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.