Capafy User
Capafy buyer workflows: discover Agents, purchase or renew, top up Credits, install purchased packages, manage accounts/orders/subscriptions/instances, review services, and open web-only buyer operations. Handles conversations with purchased cloud Agents when no matching local Thin Skill exists. Use a matching Thin Skill for its conversations. Publishing and developer workflows belong to capafy-publisher; this Skill only handles that handoff.
Install
npx skills add Capafy/Capafy-skills --skill capafy-usergit clone --depth 1 https://github.com/Capafy/Capafy-skills.git /tmp/Capafy-skills
mkdir -p ~/.claude/skills
cp -r /tmp/Capafy-skills/capafy-user ~/.claude/skills/capafy-userPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Capafy Buyer Skill Read the matching workflow reference when needed; do not preload every reference or the entire API manual. Run commands from the installed Skill root; script paths are relative to that root. ## ZIP installation completion After successfully installing this skill (`capafy-user`) from a ZIP, show this standalone line before continuing with login or buyer workflows: ```text ✅ Capafy user skill installed successfully! Version <version> ``` Replace `<version>` with `version` from the installed skill's `api-docs/index.json`. For version `0.4.9`, the exact message is: ```text ✅ Capafy user skill installed successfully! Version 0.4.9 ``` Show the message only after installation succeeds. If installation fails or the installed version cannot be read, report the failure instead of claiming success or guessing a version. This message applies to installing `capafy-user` itself, not purchased Agent packages or Thin Skills. Immediately below the success line, display the installed skill's `assets/icon.png` on its own line, before any login or buyer workflow instructions. In hosts that render local Markdown images, use `` outside a code block, with blank lines around it. Replace the placeholder with the actual absolute path inside the installed `capafy-user` directory; do not use the source repository or the original attachment path. Keep angle brackets around the path so spaces are supported.
Details
- Skill name
capafy-user- Repository
- Capafy/Capafy-skills
- Path
capafy-user/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Capafy User skill do?
Capafy buyer workflows: discover Agents, purchase or renew, top up Credits, install purchased packages, manage accounts/orders/subscriptions/instances, review services, and open web-only buyer operations. Handles conversations with purchased cloud Agents when no matching local Thin Skill exists. Use a matching Thin Skill for its conversations. Publishing and developer workflows belong to capafy-publisher; this Skill only handles that handoff.
How do I install the Capafy User skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Capafy/Capafy-skills --skill capafy-user. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Capafy User popular?
It lives in Capafy/Capafy-skills, which has 49 GitHub stars and 10 forks.
Related skills
Capafy Publisher
49Capafy/Capafy-skills
Creator-side Capafy workflow for publishing, updating, packaging, uploading, re-shipping, or managing an Agent/Skill. Also handles creator earnings, payouts, statistics, refunds, certification/KYC, review links, Agent continuation, and publisher-account switching. Generic buyer login, balance, orders, purchases, subscriptions, and instances belong to capafy-user.
Memory Bank
33fockus/skill-memory-bank
Agent-agnostic long-term project memory through `.memory-bank/` + RULES (TDD/SOLID/Clean Architecture/FSD/Mobile) + dev-toolkit commands. Use when working in a project with a `.memory-bank/` directory or when the user explicitly asks for memory-bank workflow, code rules, or dev-toolkit commands (`/mb`, plan, spec, verify, done; «память проекта», «контекст проекта», «план», «продолжай по плану»).
Gtm Pipeline:people Enrichment
77keinsaasforever/gtm-pipeline-skills
Enrich contacts with work email, phone number, and/or LinkedIn URL. Use when you have a contact list that needs enrichment before outreach. Email waterfall (FullEnrich → Pipe0), phone (FullEnrich → Pipe0 → BetterContact). Enforces demo mode (email only, no phone). Also triggers on "enrich contacts", "find emails for", "get phone numbers for".
Al Agent Task
115javiarmesto/ALDC-AL-Development-Collection
Generate AL code for Business Central Agent SDK task integration. Applies the patterns from skill-agent-task-patterns to produce production-ready codeunits, page extensions, and event subscribers — verified against the runtime API availability matrix. ALDC workflow (Copilot prompt al-agent.task); invoke explicitly.
Gtm Pipeline:demo
77keinsaasforever/gtm-pipeline-skills
Generate a demo lead list of ~10 enriched contacts with personalized message examples. Use when a demo is requested, a webhook prompt describes a target audience, or someone asks to "create a demo for [client]". Enforces demo mode restrictions (email only, no phone, ~10 contacts). Chains people-search → contact-filter → people-enrichment → (optional signal-search) → message generation. Pass `--with-signals` (or ask the user) to enable a buying-intent scoring pass before message generation — pricier but produces sharper, signal-anchored messages.
Al Memory Create
115javiarmesto/ALDC-AL-Development-Collection
Generate or update memory.md file tracking decisions, changes, and learnings throughout project development for continuity across sessions. ALDC workflow (Copilot prompt al-memory.create); invoke explicitly.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.