What each component does
Installing CLI does not clone MCP/plugin repositories or register native MCP. CLI bundles evolink-cli; the MCP plugin repository provides evolink-mcp tool guidance. They remain separately maintained entry points, not an already unified skill source.
What the skills contain
Current skills cover models/parameters, image/video/audio workflows, references, estimates/approval, budget checks, original submission recovery, waiting, downloading, and original delivery. CLI includes SKILL.md and three references: capabilities, media-workflows, and usage-and-budget. See CLI skills for targets, directories, loading, and upgrades; see MCP plugins for host setup. There is no separate viral-ad, finished-UGC, automatic-editing, or preset skill library. Examples do not guarantee popularity. Code development, arbitrary file editing, and website building belong to the host rather than EvoLink tools.Shared agent instructions
Use Markdown and llms.txt
- Read the overview and choose the client/route.
- Read its setup, command/tool reference, and shared rules. Query current model schemas during execution.
- Use supported page copying or Markdown export to save a .md file for your agent. Keep Keys, tokens, and private authorization links out of it.
- llms.txt indexes documentation; it is not an MCP endpoint, CLI installer, or authentication API.