agentleFS
nicholasglazernicholasglazer/gnosis-mcp/skills/context/SKILL.md

context

Skill30 starsChanged 7 months agoMITView on GitHub

Load usage-weighted context from Gnosis MCP. Surfaces most-accessed docs for session startup or topic primers.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use feature, upgrade and 7 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.
  • bradtraversySkill

    feature

    Manage current feature workflow - start, review, explain or complete

    Also in 4 projects that use this

  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 5 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 4 projects that use this

  • MicrosoftSkill

    init

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

The file

Files
SKILL.md

Context Loading

Load a compact context summary from your knowledge base — prioritized by actual usage patterns.

Usage

/gnosis:context                          # Top docs by access frequency
/gnosis:context deployment               # Topic-focused context
/gnosis:context --category guides        # Filter by category
/gnosis:context --limit 5 auth           # Limit results

Query: $ARGUMENTS

Process

Without topic (session startup)

Get the most-accessed documents — what matters most based on real usage:

Tool: mcp__gnosis__get_context
Arguments:
  limit: 10

With topic

Get topic-relevant docs enriched with access frequency:

Tool: mcp__gnosis__get_context
Arguments:
  topic: "$ARGUMENTS"
  limit: 10

With --category flag

Tool: mcp__gnosis__get_context
Arguments:
  topic: "$ARGUMENTS"
  category: "{category}"
  limit: 10

Output Format

## Context Summary

**Top documents:**
| # | Title | Category | Accesses | Path |
|---|-------|----------|----------|------|
| 1 | Auth Guide | guides | 47 | curated/guides/auth.md |

**Stats:**
- Total docs: 571
- Total chunks: 14,582
- Categories: guides (38), architecture (12), ...

Notes

  • Access tracking is automatic — search_docs and get_doc log usage
  • First call with no access history returns empty docs + stats only
  • Disable tracking: GNOSIS_MCP_ACCESS_LOG=false
  • Purge old entries: gnosis-mcp cleanup --days 90

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.