Docs · v1.0

Welcome to Hyping.ai.

Hyping.ai is a bundle of slash commands, sub-agent definitions, and reference skills packaged as plain folders. Drop them into your AI coding agent's skills directory and call them by name. This page gets you from purchase to first skill call.

Install with the CLI (recommended)

One command installs the CLI binary, one more signs you in, one more installs the kit. Works on macOS (Apple Silicon & Intel) and Linux x86_64.

# 1. install the hypingai CLI (~58 MB binary at ~/.local/bin/hypingai)
curl -fsSL https://hyping.ai/install.sh | sh

# 2. sign in (opens browser, Google OAuth)
hypingai login

# 3. install a kit you own
hypingai install developer
# or: hypingai install marketing
# or: hypingai install combo

The CLI verifies ownership against our server, downloads a short-lived signed URL, and extracts the kit into ~/.claude/skills/. Restart your Claude Code session and every skill is available as a slash command.

Install manually (any platform)

The CLI uses this same file under the hood. To do it yourself:

  1. Sign in to your account page.
  2. Click Download next to the kit you own — you get a .zip of .md files (one per skill, with all references/*.md inlined as appendices).
  3. Unzip it. You'll get build.md, scout.md, plan.md, … one per skill.
  4. Drop the .md files where your agent expects them (paths in the Platforms section below).

Your first skill call

Once installed, start your agent and invoke a skill by name. Each skill registers a slash command using the name field in its SKILL.md — the workflow trio is ck-build, ck-scout, ck-plan.

# inside your Claude Code session, in a project root
/ck-build add user authentication with magic links

The build skill scouts your codebase, drafts a plan, spawns specialist sub-agents to implement it, runs tests where available, and self-reviews. /ck-scout is read-only exploration ("where is X defined?"); /ck-plan is pure planning into ./plans/.

What a skill looks like

A skill is a folder under ~/.claude/skills/. Open one and you'll find:

  • SKILL.md — YAML frontmatter (name, description, argument-hint) plus the instruction Markdown that primes the agent.
  • README.md — human-readable overview, usually a short summary of when to use the skill.
  • references/ — optional folder of supporting material the agent reads on demand (style guides, lookup tables, examples).

Example: ~/.claude/skills/build/SKILL.md declares name: ck-build, which is what registers the /ck-build slash command. The folder name is for the filesystem; the name field is for invocation.

Skills are plain files. Read them, fork them, edit them. No framework, no SDK, no compile step — no vendor lock-in.

Slash commands & sub-agents

Skills fall into three rough buckets — the agent picks them up automatically based on intent, or you call them explicitly.

  • Slash commands — directly callable by the user. Most-used: /ck-build (feature workflow), /ck-scout (read-only exploration), /ck-plan (planning), /ck-journal, /ck-retro, /ck-ship.
  • Sub-agents — specialist personas the agent spawns via the Task tool. Developer Kit ships: backend-developer, frontend-developer, code-reviewer, tester, debugger, docs-manager, project-manager, journal-writer, and more.
  • Reference skills — stack-specific knowledge bundles loaded automatically when relevant: shopify, threejs, shader, better-auth, tanstack, remotion, mcp-builder, react-best-practices, and more.
  • Developer workflow — 7 skills prefixed dev-: dev-plan, dev-debug, dev-loop, dev-predict, dev-scenario, dev-security, dev-autoresearch. Bundled with the Developer Kit.

On Grok (web)

Grok's Skills and Connectors page accepts one .md file per upload — exactly the format our zip ships. No re-packing needed.

  1. Sign in to your account and click Download ↓ on your kit.
  2. Unzip — you'll get 79 (or 36 / 115) individual .md files.
  3. On grok.com/skills-and-connectors, click New Skill and drop one .md at a time.

Tip: Grok uploads are one-skill-at-a-time. Start with the workflow trio (build.md, scout.md, plan.md) — these unlock most of the kit's value. Add specialists later as you need them.

On Claude Code

The CLI handles this end-to-end. After download, each build.md is auto-wrapped into build/SKILL.md inside ~/.claude/skills/ — the folder layout Claude Code expects. Restart your session and slash commands appear.

Confirm install: ls ~/.claude/skills/ — you should see folders like build, scout, plan, plus whichever kit you bought.

On Codex CLI

Codex CLI uses the same plain-Markdown skill format. Download the kit, unzip, and copy each .md into your Codex skills directory (varies by version — check codex config or ~/.codex/). No frontmatter rewriting needed — the kit's YAML is Codex-compatible out of the box.

Tip: run hypingai install <kit> --target ~/.codex/skills in a future CLI version, or just drop the .md files in by hand for now.

Other agents

Every skill is a plain .md file (with the YAML frontmatter at the top), so it works in any agent that reads a skills directory. Codex CLI, Gemini CLI, and Claude-Code forks all recognise the same format. Common paths:

  • Claude Code: ~/.claude/skills/ (expects {name}/SKILL.md layout — use the CLI to wrap automatically)
  • Codex CLI / Gemini CLI: check your tool's docs for the skills path
  • Grok web: upload .md directly

Updating

Re-run the install command. Existing skills are overwritten with the latest version. Heavy local edits won't be preserved — fork the skill to a different folder name if you need a custom version.

hypingai install developer    # pulls the latest

Uninstalling

The CLI doesn't ship an uninstall command (yet). To remove the skills, delete the folders under ~/.claude/skills/ that the kit added — a manifest file at ~/.claude/skills/.hypingai-<kit>.json lists them. To remove the CLI itself, delete ~/.local/bin/hypingai.

Support

Stuck? DM @kekius_builder on X — we read every message and reply within a business day.

Last updated · 13 May 2026