skilo
Use this skill when the user wants to share, install, inspect, publish, claim, or troubleshoot agent skills with Skilo links, refs, bundles, or tool-native skill directories.
Best use case
skilo is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when the user wants to share, install, inspect, publish, claim, or troubleshoot agent skills with Skilo links, refs, bundles, or tool-native skill directories.
Teams using skilo should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skilo/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skilo Compares
| Feature / Agent | skilo | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when the user wants to share, install, inspect, publish, claim, or troubleshoot agent skills with Skilo links, refs, bundles, or tool-native skill directories.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skilo Use Skilo as the sharing layer for agent skills. ## When to use this skill Use this skill when the user wants to: - share a local skill or all skills from a supported tool - install a skill from a Skilo link, registry ref, GitHub source, `.skl` bundle, or local path - publish or claim a skill in the Skilo registry - inspect or verify a skill before installation - understand which native skill directories a tool uses - troubleshoot Skilo CLI, API, share-link, or install-target behavior ## Core workflow 1. Identify the source. Local path, `SKILL.md`, Skilo share link, `namespace/name`, GitHub source, direct URL, or `.skl` bundle. 2. Choose the operation. `share`, `add`, `import`, `inspect`, `publish`, or `claim`. 3. Choose explicit install targets when installing. Prefer tool flags over assumptions when the user names a target environment. 4. Verify before risky installation. Use `skilo inspect` when the source is untrusted or the user asks to review first. ## Commands ### Share ```bash npx skilo-cli share ./my-skill npx skilo-cli share claude npx skilo-cli share codex -y ``` Useful options: - `--one-time` - `--expires 1h` - `--uses 5` - `--password` ### Install ```bash npx skilo-cli add https://skilo.xyz/s/abc123 --cc npx skilo-cli add namespace/skill-name --codex npx skilo-cli import github:user/repo#skills/my-skill --oc npx skilo-cli import ./skill.skl --openclaw ``` `add` and `install` are interchangeable. ## Native target flags - `--cc` / `--claude-code` -> Claude Code - `--codex` -> Codex - `--cursor` -> Cursor - `--amp` -> Amp - `--windsurf` -> Windsurf - `--oc` / `--opencode` -> OpenCode - `--cline` -> Cline - `--roo` -> Roo - `--openclaw` -> OpenClaw If no explicit target flag is given, default to Claude Code. ## Native install directories - Claude Code: `~/.claude/skills/` - Codex: `~/.agents/skills/`, `~/.codex/skills/` - Cursor: `~/.cursor/skills/` - Amp: `~/.config/agents/skills/` - Windsurf: `~/.codeium/windsurf/skills/` - OpenCode: `~/.config/opencode/skills/` - Cline: `~/.cline/skills/` - Roo: `~/.roo/skills/` - OpenClaw: `~/.openclaw/skills/` ## Publishing and trust ```bash npx skilo-cli publish npx skilo-cli claim namespace/skill-name --token <claim-token> npx skilo-cli inspect https://skilo.xyz/s/abc123 ``` Key trust rules: - share links can be anonymous and claimed later - inspect untrusted skills before installation - checksums and publisher metadata should be surfaced when available ## Troubleshooting - If a share link resolves in the API but not on the site, check the site bundle and API base URL. - If `npx` behaves strangely, verify the installed package version and clear stale `_npx` cache. - If installs land in the wrong place, confirm the target flag and the tool’s native skill directory. - If a custom domain is flaky, test the worker host directly to separate DNS from application failures.
Related Skills
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
santa-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.
safety-guard
Use this skill to prevent destructive operations when working on production systems or running agents autonomously.
repo-scan
Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.
project-flow-ops
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
product-lens
Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.
openclaw-persona-forge
为 OpenClaw AI Agent 锻造完整的龙虾灵魂方案。根据用户偏好或随机抽卡， 输出身份定位、灵魂描述(SOUL.md)、角色化底线规则、名字和头像生图提示词。 如当前环境提供已审核的生图 skill，可自动生成统一风格头像图片。 当用户需要创建、设计或定制 OpenClaw 龙虾灵魂时使用。 不适用于：微调已有 SOUL.md、非 OpenClaw 平台的角色设计、纯工具型无性格 Agent。 触发词：龙虾灵魂、虾魂、OpenClaw 灵魂、养虾灵魂、龙虾角色、龙虾定位、 龙虾剧本杀角色、龙虾游戏角色、龙虾 NPC、龙虾性格、龙虾背景故事、 lobster soul、lobster character、抽卡、随机龙虾、龙虾 SOUL、gacha。
manim-video
Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
laravel-plugin-discovery
Discover and evaluate Laravel packages via LaraPlugins.io MCP. Use when the user wants to find plugins, check package health, or assess Laravel/PHP compatibility.