cta-format

Standardize Next Step CTA blocks with task-ID binding and FAIL-Routing rules.

11|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Arcanada-one/datarim --skill cta-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cta-format
Source: https://github.com/Arcanada-one/datarim/tree/main/skills/cta-format
Command: npx skills add https://github.com/Arcanada-one/datarim --skill cta-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves inconsistent, hard-to-follow “what should I do next?” instructions by enforcing a single canonical Next Step CTA block across every pipeline command and agent.

Core Features & Use Cases

  • Canonical CTA rendering: Produces a predictable numbered Next-Step menu with exactly one primary recommended action.
  • Task-accurate context: Binds each actionable command to the correct active task ID and stage.
  • Operator-friendly safety: Handles multi-task scenarios with a dedicated “Другие активные задачи” section and provides specialized FAIL-Routing CTA shapes for QA/Compliance failures.

Quick Start

Use the cta-format skill to ensure every dr-* command output ends with the standardized Russian “Следующий шаг — {TASK-ID}” CTA block that your operator can copy-paste directly.

Frequently Asked Questions about cta-format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize next-step CTA formatting across multi-task workflows?

Standardize next-step CTA formatting by enforcing a canonical header and footer structure with task-ID binding, ensuring operators select the correct dr-* command across multi-task workflows.

What is the best way to route operators after a QA compliance failure in a pipeline?

Route operators after a QA compliance failure by applying specialized FAIL-Routing CTA shapes that propagate focus-items, guiding the operator to the correct next action.

How does human-in-the-loop task routing handle multiple active tasks?

Human-in-the-loop task routing handles multiple active tasks by rendering a dedicated section for variants, presenting exactly one primary recommended action bound to the correct active task ID.

Can I use markdown templates to enforce a single primary recommended action for CLI commands?

Use markdown templates to enforce a single primary recommended action for CLI commands by generating a predictable numbered Next-Step menu that operators can copy-paste directly.

When do I need canonical CTA blocks in workflow orchestration?

Canonical CTA blocks are needed in workflow orchestration at stage boundaries and QA outcomes when pipeline agents return control to the operator, preventing inconsistent next-step instructions.