getting-started

Guide mandatory agent skill activation for code-related tasks.

10|2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/raddue/crucible --skill getting-started-raddue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: getting-started
Source: https://github.com/raddue/crucible/tree/main/skills/getting-started
Command: npx skills add https://github.com/raddue/crucible --skill getting-started-raddue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that you consistently leverage the power of agent skills for any task involving code, preventing the bypass of crucial development and review processes.

Core Features & Use Cases

  • Mandatory Skill Invocation: Enforces the rule to activate relevant skills before any code-related action or response.
  • Clear Decision Framework: Provides a simple test to determine when a skill applies and when direct response is appropriate.
  • Use Case: Before writing any new code for a feature, you would invoke the design → build skill to ensure the process is followed correctly.

Quick Start

Always invoke a relevant skill before writing, modifying, or debugging code.

Frequently Asked Questions about getting-started

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

FAQPage Schema
When do I need to invoke a skill for code-related tasks?

Skill invocation is mandatory before any code-related action including design, implementation, and debugging. You must activate relevant skills before writing or modifying code to prevent bypassing crucial development and review processes.

How do I know if a task requires skill invocation or a direct response?

Use the clear decision framework provided to test whether a task requires skill activation. If the task involves writing, modifying, or debugging code, invoke a relevant skill; otherwise, a direct response is appropriate.

What is the best way to enforce process discipline during software development?

The best way to enforce process discipline is by mandating skill invocation before acting on code tasks. This establishes a clear protocol for activation and applies iterative quality gates throughout development.

Can I start writing new code for a feature without activating a skill?

No, you cannot start writing new code without skill activation. For example, before writing code for a feature, you must invoke the design to build skill to ensure the process is followed correctly.

Why does bypassing skill invocation cause issues in the development workflow?

Bypassing skill invocation causes workflow issues because it skips crucial development and review processes. Invoking skills ensures consistent process discipline and iterative quality gates are applied to all code-related tasks.