Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

ratel-ai

@ratel-ai source repo

7 published skills

  1. ▌
    Changelog · ratel-ai bundle
    Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc.* sections into a single X.Y.Z section). Invoke before tagging a release.
    0
    installs
  2. ▌
    Ops Publish To Ametyst · ratel-ai
    Publish local .claude skills/loops to Ametyst — verbatim, flattened, no brain rewrite; optional retire-local (MOVE originals to deprecated-skills/, never delete) makes Ametyst the source of truth.
    0
    installs
  3. ▌
    Ratel Integrate · ratel-ai bundle
    Inspect an existing agent codebase, map each agent's tools and skills, then implement Ratel so every agent discovers and loads only its intended capabilities. Use when asked to add, wire, set up, or integrate Ratel; connect existing tools or SKILL.md playbooks to an agent through Ratel; or migrate a Vercel AI SDK, Mastra, custom TypeScript, or Python agent to Ratel. Prefer Ratel's official TypeScript adapters for AI SDK and Mastra. Edits code and dependencies, preserves capability boundaries, and verifies the result. Excludes telemetry, experiments, pilots, A/B tests, and rollout planning.
    0
    installs
  4. ▌
    Ratel Assessment · ratel-ai bundle
    Read a partner's agent codebase, score it across the 12-dimension catalog, and emit an evidence-cited markdown plus branded scored HTML report. Use for a first-touch audit: assess/review/audit our agent, where to improve, spot low-hanging fruit, an honest read of what's weak, what Ratel would notice, or `/ratel-assessment`. Static-only unless a live telemetry sample (any OTLP/OTel backend — Ratel, Langfuse, LangSmith) is MCP-wired; writes to <repo>/.ratel/ without editing code; routes into follow-up Ratel skills.
    0
    installs
  5. ▌
    Ratel Decompose Prompt · ratel-ai bundle
    Break a bloated, monolithic agent system prompt into a lean stable core plus extracted Ratel-style skills. Use when a prompt is too long or does too many things, to extract or factor procedures into skills, decompose or split a prompt, cut per-turn token cost, or `/ratel-decompose-prompt`. Writes a markdown decomposition plan (lean core, skill inventory, per-skill SKILL definitions, registration wiring) to <repo>/.ratel/ without rewriting the prompt or code. Reached from /ratel-assessment's Prompt Decomposition dimension; pairs with /ratel-tune-definitions.
    0
    installs
  6. ▌
    Ratel Tune Definitions · ratel-ai bundle
    Audit a codebase's tool and skill definitions against a failure-mode rubric and write a markdown tuning plan with per-definition before/after rewrites that make them retrievable by Ratel's hybrid lexical + semantic index and usable by the model. Use when the model picks the wrong tool, tools never get picked, descriptions are too long/vague/anemic, to fix near-duplicates, tighten schemas/enums/param names, clean up the tool catalog, or `/ratel-tune-definitions`. Fetches live Ratel docs; writes to <repo>/.ratel/ without editing tool or skill code. The fix /ratel-assessment's Definition Quality dimension routes to; runs after /ratel-decompose-prompt.
    0
    installs
  7. ▌
    Ratel Observability Assessment · ratel-ai bundle
    Inspect an agent codebase to decide where tracing belongs, turn on Ratel's native OTLP telemetry, and pick the OTel backend the team already runs to export to, then write a proposal covering instrumentation, backend selection, and the dashboards that prove value. Use when mounting observability, asking where tracing goes or what to instrument/measure, turning on Ratel telemetry, choosing an OTel backend (Langfuse/LangSmith/collector/Ratel Cloud), designing dashboards, asking what proves Ratel's value, or `/ratel-observability-assessment`. Independent observability branch reached from /ratel-assessment; may point to /ratel-integrate when the user separately wants code integration. Writes one living markdown file to <repo>/.ratel/; does not edit code or call a backend API; skips when there's no agent surface.
    0
    installs