vexor-cli
Skill1 starsChanged 2 months agoMPL-2.0View on GitHub
Use when the user asks to locate, discover, map, or find where something is implemented, loaded, defined, documented, configured, routed, or referenced in a medium or large repository and the file location is unclear. Use semantic file discovery via `vexor` for intent-based searches, unfamiliar codebases, broad feature location, architecture entrypoints, docs sections, config loaders, command definitions, and file discovery before deeper inspection. Do not use when the exact filename or text pattern is already known, for small obvious repos, for simple `rg` text searches, for non-repository web research, or for editing files after discovery. If the primary task is graph-backed dependency impact or blast-radius analysis, use code-review-graph. If the primary task is project-docs-backed questioning, use grill-with-docs.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/react-native-skills/AGENTS.mdAGENTS.md
- .agents/skills/vercel-optimize/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- ai-coding-disciplineSkill
- artifact-system-designerSkill
- artifact-validation-workflowSkill
- catalogue-routerSkill
- chat-export-capability-minerSkill
- cli-creatorSkill
- code-review-graphSkill
- codex-coding-os-masterSkill
- codex-design-artifactsSkill
- vercel-composition-patternsSkill
- create-prdSkill
- crisis-command-centerSkill
- customer-journey-mapSkill
- deep-criticSkill
- defensive-security-checklistSkill
- docSkill
- evidence-checkerSkill
- external-skill-overlay-packSkill
- grill-meSkill
- grill-with-docsSkill
- humanizerSkill
- improve-codebase-architectureSkill
- new-project-documentation-systemSkill
- pdfSkill
- playwrightSkill
- postgres-security-best-practicesSkill
- pre-mortemSkill
- process-docsSkill
- product-strategySkill
- project-session-continuitySkill
- quality-improvement-problem-solvingSkill
- quant-reviewSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- security-best-practicesSkill
- security-ownership-mapSkill
- security-threat-modelSkill
- ssot-auditorSkill
- ssot-drafterSkill
- storyscope-structural-auditSkill
- support-docsSkill
- technical-docs-packSkill
- vercel-optimizeSkill
- wbs-artifact-plannerSkill
- working-backwardsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.