agentleFS
Sign inStart free
PlayUGCAIPlayUGCAI/bloxkit-ai/skills/test/SKILL.md

test

Skill0 starsChanged 6 months agoMITView on GitHub

Validate the current project and build a fresh place file. Use when the user wants to run /test from a Bloxkit repo or project.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure 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.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 2

    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. Distinctive:

    Use the shared Bloxkit workflow runner instead of rebuilding this flow manually.

    line 8
  2. Very specific:

    Run node toolkit-v2/scripts/command-runner.mjs /test with any user arguments filled in.

    line 13
  3. Distinctive:

    Do not substitute lower-level scripts unless you are debugging the shared workflow.

    line 14

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

/test

Use the shared Bloxkit workflow runner instead of rebuilding this flow manually.

Workflow:

  1. Confirm you are in the current Bloxkit project root.
  2. Run node toolkit-v2/scripts/command-runner.mjs /test with any user arguments filled in.
  3. Do not substitute lower-level scripts unless you are debugging the shared workflow.
  4. Return the command summary, changed artifacts, and any remaining manual Studio or MCP steps.

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