Skip to main content
This page explains tools, skills, and documentation for users and agents. Reading instructions still requires actual setup, authentication, and free connection verification.

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

Bind the task to one route. CLI uses commands/local quotes; MCP uses tools/original client_request_id. Consult the appropriate reference. Installed skill files do not establish host loading, and reading skills does not configure tools or grant execution permission. Do not repeatedly generate to test discovery.

Use Markdown and llms.txt

  1. Read the overview and choose the client/route.
  2. Read its setup, command/tool reference, and shared rules. Query current model schemas during execution.
  3. 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.
  4. llms.txt indexes documentation; it is not an MCP endpoint, CLI installer, or authentication API.

Verify after updates

Synchronize bundled skills after a CLI upgrade and reload them in the host. After plugin/manual MCP changes, check the current connection, OAuth, and permissions. Preserve other services and personal edits. Package, documentation, and tool versions can differ; resolve conflicts against actual released versions and returned schemas and explain uncertainty.