agentleFS
variaty-appvariaty-app/variaty-company-brain/skills/discord-search/SKILL.md

discord-search

Skill0 starsChanged 5 months agoMITView on GitHub

Use when answering questions about Discord conversations, messages, channels, threads, or decisions — what someone said, what was decided, or to summarize a channel. Drives the discord-search MCP server tools (search_messages_tool, get_thread_tool, get_message_tool, list_channels_tool).

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. merchako/agent-skills★ 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Every result is already filtered by OpenFGA to exactly the channels, threads, and messages you are allowed to read — the tools never return …

    line 9
  2. Very specific:

    Call list_channels_tool first when the channel/thread is unclear — discover what is readable before searching.

    line 31
  3. Very specific:

    Call search_messages_tool with focused keywords.

    line 33
  4. Very specific:

    Read full text with get_message_tool(message_id) or get_thread_tool(thread_id, detail="full") before quoting — search returns snippets.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Discord search

Answer questions about your team's Discord using the discord-search MCP server. Every result is already filtered by OpenFGA to exactly the channels, threads, and messages you are allowed to read — the tools never return anything you lack access to.

When to use

Questions about conversations, messages, channels, threads, decisions, or what specific people said on Discord. Examples: "what did Eva say about the launch?", "summarize #all-hands this week", "when did we decide on Postgres?", "who owns the Apollo project?".

Tools (discord-search server)

ToolPurpose
list_channels_toolList the channels (and optionally threads) you can read. Start here when the question names a channel/thread vaguely. Arg: include_threads.
search_messages_toolSearch messages. Returns snippet-first stubs (message_id, snippet, author, created_at) — not full bodies. Args include query, author, channel_id, thread_id, semantic, limit, sort, and time filters. Pass semantic=true for meaning-based (hybrid BM25 + vector) search.
get_message_toolFetch one full message by message_id.
get_thread_toolFetch a thread's messages by thread_id; pass detail="full" for full text.

Claude surfaces these prefixed by the server, e.g. …discord-search__search_messages_tool.

Workflow

  1. Call list_channels_tool first when the channel/thread is unclear — discover what is readable before searching.
  2. Call search_messages_tool with focused keywords. Use semantic=true for conceptual questions; narrow with author, channel_id, or time filters.
  3. Read full text with get_message_tool(message_id) or get_thread_tool(thread_id, detail="full") before quoting — search returns snippets.
  4. Time filters: pass last_days OR after/before/on — never both.

Rules

  • Results are already masked to what you may read. Never speculate about channels or messages that do not appear in results.
  • Quote exactly; cite the channel/thread and the timestamp from the tool output.
  • Empty results mean "nothing found or nothing readable" — say so plainly, do not guess.
  • A message you can't find may simply be one you lack access to — phrase as "I couldn't find or access it", never "it doesn't exist".

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.