Directory entries and verified installation
Directory entries enable open discovery and comparison. When installing, select verified releases with signed manifests and review records.
BUILT FOR AGENTS
Readable by humans. Native to agents.
Deliver a structured capability directory directly to your agent. Plain text, JSON indexes, and feeds generated from the exact same source.
01 / START HERE
Ask your AI to explore
Copy this prompt into any AI agent with web or context reading capabilities, then describe your task.
AGENT PROMPT
Read https://skillflux.app/llms.txt first, then use https://skillflux.app/index.json to find agent capabilities (skills, MCP tools, plugins) relevant to my task. Compare purpose, source type, and limitations; include original links and recommendations. Yellow pages inclusion does not imply official endorsement. Before installation, check qualification and ask me to approve the plan.
02 / OPEN ENDPOINTS
Choose the right format
TXT
/llms.txt
Start here for the site's purpose, main entry points and data boundaries.
TXT
/llms-full.txt
The complete source catalog in plain text, ready to read, search and cite.
JSON
/index.json
Source names, types, tags, summaries and links, plus scenario and skill-release entry points.
RSS
/feed.xml
An RSS feed of source entries for following additions and updates.
RSS
/insights/feed.xml
RSS for editorial analysis and workflows. Articles are not install-package evaluations.
JSON
/skills-index.json
Skills and version states from a signed publication snapshot. Recheck live qualification before installation.
JSON
/scenarios/index.json
Task-based scenarios, selection and maintenance guides, with Chinese and English page links.
03 / READ WITH CONTEXT
Understand the data and its limits.
Snapshots have a timestamp
Pages and JSON are generated at build time. Keep source links and timestamps when citing, and let the runtime check live status before installing or upgrading.
Reading and acting are separate
Public endpoints provide data. Connecting a project, installing and upgrading require explicit user intent, project permissions and exact-version plans.
Want to equip your agent directly?
Read the setup guide