how the skill or plugin itself is built
make-skill
A skill that builds skills: create, retrofit, audit and publish agent skills and Claude Code plugins — Agent Skills standard conformance, marketplace layout, version sync, validator + CI, every distribution channel, MCP and A2A rules.
Install this pack on its own, or use it with the ssheleg harness.
What it ships
Each name below is an entry point an agent can be routed to.
Shape: static. The standard is a checklist and the audit walks it in order; a skill that passes is auditable against the same list next time.
make-skill
Use when creating, upgrading, auditing, or publishing agent skills and Claude Code plugins - / «», or when a skill must reach an MCP server or another agent over A2A. NOT for a version bump or release in a repo that ships anything but a skill or plugin. Encodes the Agent Skills standard, Anthropic's platform rules (limits, budgets, Skills API, evals), the plugin reference (manifests, layout, validate --strict), plus the ssheleg pipeline - marketplace layout, version sync, validator+CI, distribution, npm gotchas.
Install just this one
Every pack installs standalone. The whole family is one command.
npx skills add ssheleg/make-skill
claude plugin marketplace add ssheleg/make-skill && claude plugin install make-skill@make-skill
When the agent reaches for it
These are the rules the family writes into your agent's own instruction file — verbatim. Each one states the rule, the boundary in both directions, and the phrase that declines it.
/make-skill — how the skill itself is built
- when: a skill or plugin changes shape
- decline it: no make-skill
If make-skill is installed, skill/plugin construction goes through it — create, retrofit, conformance audit («аудит скилов»), plugin wrapping, version sync, validator+CI, all-channel publication. It owns front-matter limits, claude plugin validate --strict, and plain ~/.claude/skills/ shadowing.
The boundary. NOT through it: USING a skill, ordinary repo code, doctrine edits in a conformant skill.
Refusal phrase: "no make-skill" or «без make-skill».
Among the routers: make-skill checks construction; task-pipeline delivers. A skill release takes both.
The rest of the family
super-ux v0.59.1
Scenario-driven UI development: a versioned design chain in docs/ux/ — the product vision, personas and jobs, user flows and the paid-acquisition funnel among them, a screens-and-states map with Figma frames…
task-pipeline v1.90.2
Full-cycle delivery orchestrator: an intake grill turns the request into a complete brief, then ten gated stages carry it from docs to acceptance, refusing to advance until each gate passes.
agent-sync v1.21.5
Coordination plane for concurrent agents: leases with a TTL so two agents cannot claim the same work, race-free id reservation, a run journal and a generated board, over a pluggable knowledge cloud.
sheleg-design v1.64.0
The taste layer: cinematic scroll-driven landing pages (one scroll clock, motion that degrades to calm, WebGL particle formations), product-UI style packs with a ready token layer each, and the Figma border
seo-aeo-audit v0.26.3
Evidence-first website audit for search and answer engines: ten tracks from crawl access to AI citation mechanics, every finding backed by an observation and every recommendation tiered, ending in…
sheleg-dev v0.13.2
The integration layer a product reaches once it has users: Stripe subscription billing reconciled into your own database
agent-stack v0.25.5
Production patterns for AI agent systems, in four skills. The orchestrator: tool-calling loops that survive context pressure, pipelines with human checkpoints and resume, provider routing with fallback…
telegram-dev v0.2.2
Telegram, split by the API each surface actually speaks, in three skills. telegram-bots covers the official HTTP Bot API
xr-dev v0.3.2
Quest product delivery from platform choice to launch and operation, with stage owners, evidence gates and next actions.
web3d-dev v0.1.2
Realtime 3D on the web with three.js and React Three Fiber, in three skills split by the question. web3d-runtime owns how the scene runs