agentleFS
Sign inStart free
Nyquest-aiNyquest-ai/nyquest-claude-mcp/skills/level/SKILL.md

level

Skill2 starsChanged 17 days agoMITView on GitHub

Set the Nyquest context-manager slider (0 = off, 0.5 default, 1 = most aggressive). Use when the user runs /nyquest:level or asks to change how aggressively tool results are parked.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tov-guidelines, icp-research and 3 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.
  • matteotittaSkill

    tov-guidelines

    Analyzes existing client content (website, blog, social, docs) to extract voice patterns, vocabulary preferences,

    Also in 3 projects that use this

  • 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 versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. matteotitta/claude-code-marketing-quickstart★ 70same name
    2. matteotitta/repo-structure-in-house★ 70same name
    3. ProjectAJ14/eklavya★ 29same name
    4. matteotitta/repo-structure-agency★ 1same name
    5. 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    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:

    Call the Nyquest configure tool with level set to the requested value (a number between 0 and 1).

    line 8

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

Call the Nyquest configure tool with level set to the requested value (a number between 0 and 1). If no value was given, call configure with no arguments to show the current settings and explain the scale:

  • 0: off
  • 0.3: only huge results (over ~4,000 tokens), deterministic digests
  • 0.5 (default): results over ~1,500 tokens; logs, data and prose; code listings untouched
  • 0.8: results over ~750 tokens, code listings parked with a definition index
  • 1.0: results over ~500 tokens, everything eligible

At every level a park must save at least minSavingTokens (default 300) after paying for the digest and the parking note, and targeted reads (grep, sed -n, head, tail) under 8 KB are never parked.

Report the resulting setting in one line. If the user asks about the API key or full mode instead, that is /nyquest:setup.

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