skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
CowAgent is your own open-source personal AI agent. It plans tasks proactively, uses tools, skills and MCP, and gets to know you over time through long-term memory, a knowledge base and self-evolution. It's also an open, extensible Agent Harness.
CowAgent is multi-model, multi-channel and multi-agent, lightweight and built to extend. Plug in any major LLM provider, run it 24/7 on your computer or server, and reach it from the web and all major IM platforms.
🎬 Demo
🌟 Highlights
| Capability | Description |
|---|---|
| Planning | Decomposes complex tasks and executes them step by step, looping over tools until the goal is reached |
| Multi-Agent | Build a team of Agents, each with its own role, model, skills, and knowledge, collaborating within a shared conversation |
| Memory | Three-tier architecture (context → daily → core), automatic Deep Dream distillation, hybrid keyword + vector retrieval |
| Knowledge | Auto-curates structured knowledge into a Markdown wiki, builds an evolving knowledge graph with visual browsing |
| Evolution | Self-Evolution reviews conversations automatically to improve skills, follow up on unfinished tasks, and consolidate memory and knowledge, growing through everyday use |
| Skills | One-click install from Skill Hub, GitHub, ClawHub; or create custom skills via natural-language conversation |
| Tools | Built-in file I/O, terminal, browser, scheduler, memory retrieval, web search, and 10+ more tools — with native MCP integration |
| Channels | Integrates with Web, WeChat, Feishu, DingTalk, WeCom, QQ, Official Accounts, Telegram, and Slack |
| Multimodal | First-class support for text, images, voice, and files — recognition, generation, and delivery |
| Models | Claude, GPT, Gemini, DeepSeek, Qwen, GLM, Kimi, MiniMax, Doubao, and more — swap providers from the Web console with one click |
| Deploy | One-line installer or desktop client, unified Web console, multiple deployment modes (local, Docker, server) |
🏗️ Architecture
CowAgent is a complete Agent Harness: messages flow in through Channels; the Agent Core plans and reasons over memory, knowledge, and the available tools and skills; Models generate the response, which is sent back through the originating channel. Every layer is decoupled and independently extensible.
Read more in Architecture.
🚀 Quick Start
A one-line installer takes care of dependencies, configuration, and startup:
Linux / macOS:
bash <(curl -fsSL https://cdn.link-ai.tech/code/cow/run.sh)
Windows (PowerShell):
irm https://cdn.link-ai.tech/code/cow/run.ps1 | iex
Docker:
curl -O https://cdn.link-ai.tech/code/cow/docker-compose.yml
docker compose up -d
Once started, open http://localhost:9899 to access the Web console — your one-stop hub to chat with the Agent, configure models, connect channels, and install skills.
Deploying on a server? Set
web_hostto0.0.0.0inconfig.jsonto make the console reachable from outside, and setweb_passwordto protect it. Don't forget to open port9899in your firewall or security group.
📖 Detailed guides: Quick Start · Install from Source · Upgrade
After installation, manage the service with the cow CLI:
cow start | stop | restart # service control
cow status | logs # status and logs
cow update # pull latest code and restart
cow skill install <name> # install a skill
cow install-browser # install browser automation
💻 Desktop client: download the CowAgent Desktop client (macOS / Windows) — the backend is bundled, ready to use out of the box.
☁️ Prefer not to deploy? Open the cloud console to create a dedicated instance with built-in models, online 24/7.
👥 Multi-Agent Team
Create a team of Agents, each with its own memory, capabilities, knowledge, and workspace. Each can focus on its own domain, or collaborate within a shared conversation to tackle complex tasks together. Multi-Agent teams are available on the Web, the desktop client, and IM channel integrations.
See Agent Team for details.
🤖 Models
CowAgent supports all mainstream LLM providers. Chat, vision, image generation, ASR/TTS, and embeddings can each be routed to a different vendor. Providers are configured directly in the Web console — no manual file editing required.
| Provider | Featured Models | Chat | Vision | Image Gen | ASR | TTS | Embedding | | --- | --
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/skill-creator/SKILL.md7.9 KBupstream ↗
--- name: skill-creator description: Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task. license: Complete terms in LICENSE.txt --- # Skill Creator This skill provides guidance for creating effective skills using the existing tool system. ## About Skills Skills are modular, self-contained packages that extend the agent's capabilities by providing specialized knowledge, workflows, and tools. They transform a general-purpose agent into a specialized agent equipped with procedural knowledge. ### What Skills Provide 1. **Specialized workflows** - Multi-step procedures for specific domains 2. **Tool integrations** - Instructions for working with specific file formats or APIs 3. **Domain expertise** - Company-specific knowledge, schemas, business logic 4. **Bundled resources** - Scripts, references, and assets for complex tasks ### Core Principle **Concise is Key**: Only add context the agent doesn't already have. Challenge each piece of information: "Does this justify its token cost?" Prefer concise examples over verbose explanations. ## Skill Structure Every skill consists of a required SKILL.md file and optional bundled resources: ``` skill-name/ ├── SKILL.md (required) │ ├── YAML frontmatter metadata (required) │ │ ├── name: (required) │ │ └── description: (required) │ └── Markdown instructions (required) └── Bundled Resources (optional) ├── scripts/ - Executable code (Python/Bash/etc.) ├── references/ - Documentation intended to be loaded into context as needed └── assets/ - Files used in output (templates, icons, fonts, etc.) ``` ### SKILL.md Components **Frontmatter (YAML)** - Required fields: - **name**: Skill name in hyphen-case (e.g., `weather-api`, `pdf-editor`) - **description**: **CRITICAL** - Primary triggering mechanism - Must clearly describe what the skill does - Must explicitly state when to use it - Include specific trigger scenarios and keywords - All "when to use" info goes here, NOT in body - Example: `"PDF document processing with rotation, merging, splitting, and text extraction. Use when user needs to: (1) Rotate PDF pages, (2) Merge multiple PDFs, (3) Split PDF files, (4) Extract text from PDFs."` **Body (Markdown)** - Loaded after skill triggers: - Detailed usage instructions - How to call scripts and read references - Examples and best practices - Use imperative/infinitive form ("Use X to do Y") ### Bundled Resources **scripts/** - When to include: - Code is repeatedly rewritten - Deterministic execution needed (avoid LLM randomness) - Examples: PDF rotation, image processing - Must test scripts before including **references/** - When to include: - **ONLY** when documentation is too large for SKILL.md (>500 lines) - Database schemas, complex API specs that agent needs to reference - Agent reads these files into context as needed - **NOT for**: API reference docs, usage examples, tutorials (put in SKILL.md instead) - **Rule of thumb**: If it fits in SKILL.md, don't create a separate reference file **assets/** - When to include: - Files used in output (not loaded to context) - Templates, icons, boilerplate code - Copied or modified in final output **Important**: Most skills don't need all three. Choose based on actual needs. ### What NOT to Include Do NOT create auxiliary documentation files: - README.md - Instructions belong in SKILL.md - INSTALLATION_GUIDE.md - Setup info belongs in SKILL.md - CHANGELOG.md - Not needed for local skills - API_REFERENCE.md - Put API docs directly in SKILL.md - USAGE_EXAMPLES.md - Put examples directly in SKILL.md - Any other documentation files - Everything goes in SKILL.md unless it's too large **Critical Rule**: Only create files that the agent will actually execute (scripts) or that are too large for SKILL.md (references). Documentation, examples, and guides ALL belong in SKILL.md. ## Installing a Skill Install target directory: `<workspace>/skills/<name>/` (the `<workspace>` is from the "Workspace" section). ### Step 1 — Obtain skill content | Source | Action | |---|---| | URL (single file) | Fetch content via curl or web_fetch | | URL (zip/archive) | Download and extract to a temp directory | | Local file (SKILL.md) | Read directly | | Local archive (zip) | Extract to a temp directory | ### Step 2 — Identify and install 1. Locate the SKILL.md (may be at top level or inside a subdirectory) 2. Extract `name` from YAML frontmatter 3. Copy the **entire skill directory** (SKILL.md and all sibling files/folders such as `references/`, `scripts/`, `assets/`, etc.) into `<workspace>/skills/<name>/` 4. If an install/setup file exists (e.g. INSTALL.md), follow its instructions — the final result must still end up in `<workspace>/skills/<name>/` ## Skill Creation Process (from scratch) 1. **Understand** - Clarify use cases with concrete examples 2. **Plan** - Identify needed scripts, references, assets 3. **Initialize** - Run init_skill.py to create template 4. **Edit** - Implement SKILL.md and resources 5. **Validate** (optional) - Run quick_validate.py to check format 6. **Iterate** - Improve based on real usage ## Skill Naming - Use lowercase letters, digits, and hyphens only; normalize user-provided titles to hyphen-case (e.g., "Plan Mode" -> `plan-mode`). - When generating names, generate a name under 64 characters (letters, digits, hyphens). - Prefer short, verb-led phrases that describe the action. - Namespace by tool when it improves clarity or triggering (e.g., `gh-address-comments`, `linear-address-issue`). - Name the skill folder exactly after the skill name. ## Step-by-Step Guide ### Step 1: Understanding the Skill with Concrete Examples Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill. To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback. For example, when building an image-editor skill, relevant questions include: - "What functionality should the image-editor skill support? Editing, rotating, anything else?" - "Can you give some examples of how this skill would be used?" - "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?" - "What would a user say that should trigger this skill?" To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness. Conclude this step when there is a clear sense of the functionality the skill should support. ### Step 2: Planning the Reusable Skill Contents To turn concrete examples into an effective skill, analyze each example by: 1. Considering how to execute on the example from scratch 2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly **Planning Checklist**: - ✅ **Always needed**: SKILL.md with clear description and usage instructions - ✅ **scripts/**: Only if code needs to be executed (not just shown as examples) - ❌ **references/**: Rarely needed - only if documentation is >500 lines and can't fit in SKILL.md - ✅ **assets/**: Only if files are used in output (templates, boilerplate, etc.) Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows: 1. Rotating a PDF requires re-writing the same code each time 2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill 3. ❌ Don't create `references/api-docs.md` - put API info in SKILL.md insteadREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/zhayujie-cowagent-skills-skill-creator.md