agentleFS
ibra-zhanibra-zhan/reazon/skills/level/SKILL.md

level

Skill4 starsChanged 25 days agoMITView on GitHub

See or change your Reazon level (beginner, intermediate, advanced), for you personally or just for this project.

4 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use icp-research, messaging and 2 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.
  • growthack88Skill

    icp-research

    Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. Upstream: recommended company-context. Downstream: feeds positioning, product-messaging, landing-page-copy, content-strategy, and outreach-emails.

    Also in 3 projects that use this

  • VercelSkill

    messaging

    Use when turning settled positioning into the lines other people will reuse: the message hierarchy, value propositions per audience, objection handling, and the proof behind each claim.

    Also in 3 projects that use this

  • VercelSkill

    positioning

    Use when working out what a product is, who it's for, and what it competes with: the market alternatives, the ideal customer, the differentiators worth claiming, and the positioning statement that follows.

    Also in 3 projects that use this

  • YepAPISkill

    competitor-research

    Competitive analysis between domains using YepAPI.

    Also in 3 projects that use this

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. ProjectAJ14/eklavya★ 29same name
    2. Nyquest-ai/nyquest-claude-mcp★ 2same name
    3. matteotitta/repo-structure-agency★ 1same name
    4. dachi-jp3/cogito★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run reazon level to see the current level and its source.

    line 13
  2. Very specific:

    Ask with AskUserQuestion (header Level, multiSelect: false):

    line 14
  3. Very specific:

    Run reazon level --set <level> (add --project for this project only), or reazon level --clear-project to remove the override.

    line 21

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

Reazon level

The helper is node "${CLAUDE_PLUGIN_ROOT}/bin/reazon.mjs" <command> --cwd "<absolute project folder>", written below as reazon <command>. Quote paths. It prints JSON; on "ok": false, explain the error and stop. Don't edit Reazon files by hand as a fallback.

  1. Run reazon level to see the current level and its source.
  2. Ask with AskUserQuestion (header Level, multiSelect: false):
    • Beginner: "I can write small programs but haven't built a full app."
    • Intermediate: "I've built apps, but I'm not confident about architecture choices."
    • Advanced: "I design systems; challenge my assumptions instead of explaining."
  3. Then ask, also with AskUserQuestion (header Applies to): Everywhere (your personal level) or Just this project (for a stack you're newer or stronger in). If a project override exists, add Remove project override.
  4. Run reazon level --set <level> (add --project for this project only), or reazon level --clear-project to remove the override.
  5. Confirm in one line what changed. Existing decisions keep the level they were written at; new ones use the new level.

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.