claude-code-helper

To create Claude Code skills, you must define specific YAML frontmatter fields that dictate how the skill behaves. This configuration establishes the skill's operational parameters and enables it to extend the CLI's core functionality.

Claude Code subagents extend functionality by running forked processes with specific context, while hooks integrate with tool workflows to trigger actions. Both mechanisms modify CLI behavior but serve distinct operational purposes within your automation.

Configuring MCP in Claude Code CLI involves integrating external tool workflows through specific setup commands. This process connects your Model Context Protocol servers to the CLI, enabling extended tool access and dynamic command output during your sessions.

Common Claude Code slash commands include /permissions for managing access rules, /agents for viewing subagents, /context for managing session context, and /init for initializing project configurations. These commands control core CLI operational behaviors.

Yes, Claude Code CLI supports dynamic command output generated during forked subagent runs. This capability allows subagents to execute tasks and return context-specific results that integrate directly into your active workflow.

Claude Code skills may fail to trigger if the required YAML frontmatter is missing or incorrectly configured. You must ensure the skill configuration matches the expected CLI workflows and operational context requirements for accurate invocation.