agentleFS
ZhixiangLuoZhixiangLuo/10xProductivity/.cursor/skills/enterprise-search/SKILL.md

enterprise-search

Skill472 starsChanged 8 months agoMITView on GitHub

Search your entire company's institutional knowledge in one query — Slack, Confluence, Jira, Linear, Notion, GitHub, plus any AI or multi-source search tool listed in verified_connections.md. Follow workflows/enterprise-search. One question, every connected tool, synthesized answer in seconds. No tab switching. No copy-paste. Use when the user asks about a decision, an incident, a topic, a person, a past discussion, or anything that might be documented across work tools. Also triggers on: "find", "search for", "who worked on", "what was the decision about", "is there a doc on", "any Slack about".

1 other project uses a version of this.

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, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search your company's knowledge across Slack, Confluence, Jira, Linear, Notion, GitHub, and more — simultaneously, in a single query.

    line 19

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

Enterprise Search

One question. Every connected tool. One synthesized answer.

Search your company's knowledge across Slack, Confluence, Jira, Linear, Notion, GitHub, and more — simultaneously, in a single query.


Before you search: check connection status

ls verified_connections.md 2>/dev/null && grep -c "^##" verified_connections.md || echo "0"
  • 1+ tools connected → read verified_connections.md (capability index), then follow workflows/enterprise-search/enterprise-search.md for the search. That workflow always uses Slack + Confluence when connected, may include AI-synthesized search tools listed only in verified_connections.md (per each connection file), and adds Jira/Linear/Notion/GitHub when relevant.
  • Not connected / empty → read setup.md. Your agent handles the full connection flow — credentials, SSO, verification — in one session. ~5 minutes per tool.

What you can ask

  • "Search for the discussion about the database migration"
  • "Find any Jira tickets related to the login timeout bug"
  • "What was the decision about the API versioning approach?"
  • "Is there a Confluence runbook for on-call handoffs?"
  • "Who worked on the payments refactor and what did they decide?"

The search workflow handles routing, parallel execution across tools, and synthesized results. You don't need to specify which tool — the agent figures that out.

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.