agentleFS
Layneformalized225Layneformalized225/ai-cofounder/skills/exa-code-search/SKILL.md

exa-code-search

Skill1 starsChanged 8 months agoMITView on GitHub

Code search using Exa. Finds real code snippets, API docs, and examples from GitHub, StackOverflow, and technical docs. Use when searching for code examples, API syntax, library documentation, or debugging help.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Use exec to call: mcporter call exa-code.get_code_context_exa <params>

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Code Search (Exa)

Tool

Use exec to call: mcporter call exa-code.get_code_context_exa <params>

Critical Rules

  • Never run in main context. Spawn subagents or run sequentially.
  • Always include the programming language in the query to reduce noise.
    • Good: "Go generics", "Python asyncio", "React 19 hooks"
    • Bad: "generics", "async", "hooks"
  • Include framework + version when relevant: "Next.js 14", "Playwright Python".
  • Include exact identifiers (function names, error messages) when you have them.

Token Tuning

NeedtokensNum
Quick snippet1000-3000
Most tasks5000 (default)
Complex integration10000-20000

Call Syntax

# Find code example
mcporter call exa-code.get_code_context_exa \
  query="Python asyncio aiohttp client example" \
  tokensNum=5000

# API usage
mcporter call exa-code.get_code_context_exa \
  query="OpenAI Responses API streaming Python" \
  tokensNum=8000

# Debugging
mcporter call exa-code.get_code_context_exa \
  query="Next.js 14 App Router useSearchParams error boundary" \
  tokensNum=5000

# Complex integration
mcporter call exa-code.get_code_context_exa \
  query="Playwright Python page.wait_for_selector timeout handling" \
  tokensNum=15000

Output Format

Return:

  1. Best minimal working snippet(s) — copy/paste ready
  2. Notes — version constraints, gotchas
  3. Sources — URLs if present

Deduplicate similar results; keep only the best representative snippet per approach.

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.