agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/qmd/SKILL.md

qmd

Skill2 starsChanged 2 months agoMITView on GitHub

Search and retrieve this repository's author context with optional qmd, using an isolated index for each client folder.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use defuddle, obsidian-bases and 6 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.
  • HK-hubSkill

    defuddle

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

    Also in 4 projects that use this

  • wangzhuofengSkill

    obsidian-bases

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

    Also in 4 projects that use this

  • jykimSkill

    obsidian-cli

    Interact with Obsidian using the official CLI to read, search, create, and manage notes, daily notes, tasks, properties, and more. Use when the user wants to query or manipulate vault content via the obsidian command.

    Also in 4 projects that use this

  • wangzhuofengSkill

    json-canvas

    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

    Also in 3 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 4 projects that use this

  • VercelSkill

    vercel-react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 3 projects that use this

  • +1 more from wangzhuofeng

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Start at index.md. Use this repository's scripts/qmd.sh wrapper, which selects an index derived from the repository's absolute path.

    line 11
  2. Very specific:

    If qmd is installed, read its version-matched instructions using scripts/qmd.sh skill show or its help output.

    line 13
  3. Distinctive:

    Search known wording with:

    line 15
  4. Distinctive:

    Read full relevant files or retrieve them through the same wrapper.

    line 20
  5. Very specific:

    If qmd is missing or its index is unavailable, use rg and direct file reads.

    line 22
  6. Very specific:

    After context changes, refresh an already configured index with scripts/qmd-refresh.sh.

    line 24

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

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.

Retrieve context

Start at index.md. Use this repository's scripts/qmd.sh wrapper, which selects an index derived from the repository's absolute path. Do not use another project's global collection.

If qmd is installed, read its version-matched instructions using scripts/qmd.sh skill show or its help output. Run scripts/qmd-setup.sh when setting up the local index is part of the request.

Search known wording with:

./scripts/qmd.sh search "search terms" -c context

Read full relevant files or retrieve them through the same wrapper. A snippet is a pointer, not sufficient support for a factual claim. A stub is an unanswered prompt, not author context.

If qmd is missing or its index is unavailable, use rg and direct file reads. Do not install software, download models or configure global MCP servers just to answer a context question.

After context changes, refresh an already configured index with scripts/qmd-refresh.sh. Moving the repository creates a different index name; run setup at the new location. Use scripts/qmd.sh --print-index to inspect the index name without running qmd.

Answer with source paths and relevant uncertainty. For current external facts, verify using appropriate sources rather than treating an old local snapshot as current.

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.