← ClaudeAtlas

skill-creatorlisted

Profile skill management via `skill.profile.*` and `skill.marketplace.*`. Use when listing, inspecting, creating, editing, deleting, or installing custom skills. Every skill must keep `name` and `description` in YAML frontmatter because AgentLoop summaries are built from that metadata.
afkbot-io/afkbotio · ★ 3 · AI & Automation · score 67
Install: claude install-skill afkbot-io/afkbotio
# skill-creator Purpose: manage profile-local skills stored as markdown files under `profiles/<profile_id>/skills/<name>/SKILL.md`. ## Workflow 1. Always inspect skills first with `skill.profile.list`, `scope=all`. - For generic requests like "какие навыки есть" or "покажи навыки", never use `scope=profile` unless the user explicitly asked for only profile-local skills. 2. Before create/edit/delete, return a short summary of existing skills from list payload: - `name` - `summary` 3. If user asks to inspect one skill, call `skill.profile.get`. 4. If user asks to create or edit a skill, call `skill.profile.upsert` with: - `name`: normalized slug that matches `^[a-z0-9][a-z0-9-]*$`. - `markdown`: complete skill body in markdown. 5. If user asks to remove a skill, call `skill.profile.delete`. 6. If user asks to browse marketplace skills, call `skill.marketplace.list`. 7. If user asks to search/filter marketplace skills, call `skill.marketplace.search`. 8. If user asks to install a marketplace skill, call `skill.marketplace.install`. Marketplace defaults: - If user did not provide a source, use the default curated marketplace source. - Prefer `skill.marketplace.list` before install when the user asks to browse. - Prefer `skill.marketplace.search` when the user already provided a query. - If user names a skill directly, install it without asking for a raw marketplace URL first. ## Rules - Intent routing: - If user says "сделай через скилл", treat it as explicit