agentleFS
vfarcicvfarcic/dot-ai/.claude/skills/dot-ai-query-dot-ai/SKILL.md

dot-ai-query-dot-ai

Skill336 starsChanged 10 months agoMITView on GitHub

Query sibling dot-ai projects to verify features are USABLE (not just defined). IMPORTANT: When calling this skill, explain HOW you plan to use the feature (e.g., 'I need to call X via REST API from the UI' or 'I need to import Y function'). This helps verify the full chain from definition to exposure.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Default to dot-ai (MCP server) if the target project is unclear.

    line 21
  2. Distinctive:

    Important: Do NOT use this skill to query the project you're currently working in.

    line 23
  3. Distinctive:

    When asked "does X exist?", answer:

    line 37
  4. Distinctive:

    Go deep, not wide: Follow the code path until you can prove how the caller would actually use the feature.

    line 41

≈ “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

Query dot-ai Projects

Explore the dot-ai ecosystem codebases to find the requested information.

Project Locations

Sibling projects are located in the parent directory of the current working directory (../):

  • dot-ai - Main MCP server (API endpoints, tools, handlers)
  • dot-ai-ui - Web UI for visualizations and dashboard
  • dot-ai-controller - Kubernetes controller
  • dot-ai-stack - Stack deployment configs
  • dot-ai-website - Documentation website

Default to dot-ai (MCP server) if the target project is unclear.

Important: Do NOT use this skill to query the project you're currently working in. Use local tools (Read, Grep, Glob) instead.

Excluded

dot-ai-infra - Production infrastructure. Only query if user explicitly requests it.

Verification Mindset

Don't just find that something EXISTS - prove it's USABLE.

  • Finding a type/interface is NOT enough
  • Finding internal code is NOT enough
  • You must trace from definition → implementation → exposure

When asked "does X exist?", answer:

  • "Yes, and here's how to use it: [concrete usage]" OR
  • "It exists internally but is NOT exposed for external use"

Go deep, not wide. Follow the code path until you can prove how the caller would actually use the feature.

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.