agentleFS
cyb3rcricketcyb3rcricket/cricket-mode/.agents/skills/challenge/SKILL.md

challenge

Skill0 starsChanged 50 days agoMITView on GitHub

Use when recent work looks finished but should not be trusted yet — inspect it for bugs, weak assumptions, edge cases, missing error handling, and side effects, and report findings without fixing unless asked.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, roadmap and 9 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.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

  • MetaSkill

    roadmap

    Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.

    Also in 3 projects that use this

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 3 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 4 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not assume it is correct just because it looks reasonable or passed an easy test.

    line 10
  2. Distinctive:

    Use tests, tools, or experiments when they can confirm or disprove a concern.

    line 26
  3. Distinctive:

    Do not invent problems just to be critical.

    line 28
  4. Distinctive:

    Do not automatically fix anything unless I ask.

    line 30

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

Challenge

Challenge the thing you just built, changed, or decided.

Do not assume it is correct just because it looks reasonable or passed an easy test.

Try to find what could be wrong.

Look For

  • incorrect assumptions,
  • bugs and edge cases,
  • missing error handling,
  • unintended side effects,
  • fragile logic,
  • security or reliability problems when relevant,
  • cases where the implementation technically works but does not solve the real problem.

Inspect the actual code or work when available.

Use tests, tools, or experiments when they can confirm or disprove a concern.

Do not invent problems just to be critical. Separate real findings from possibilities that still need evidence.

Do not automatically fix anything unless I ask.

Core Rule

Try to break the idea before we trust it.

Finish with:

Findings: the problems or risks you actually found.

Looks solid: anything important you challenged but could not break.

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.