Skill

chunk

Use CircleCI Chunk for AI-assisted CI/CD work through either the Chunk web UI or the chunk-cli. Trigger this skill when users ask to set up Chunk, troubleshoot or fix failing builds with Chunk, configure Chunk environments, schedule/proactively run Chunk tasks, or use chunk-cli commands such as init, validate, build-prompt, auth, sandbox, task, and skill install.

npx claudepluginhub robinebers/converted-plugins --plugin circleci

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/circleci:chunk

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Use this skill to choose the best Chunk workflow (UI or CLI), then execute it with clear prechecks and safe defaults. Keep responses action-oriented and grounded in verified commands and setup requirements.

Supporting Files

references/chunk-cli.mdreferences/chunk-ui.md

SKILL.md

49 lines · ~638 tokens

Similar Skills

product-capability

185.7k

Translates PRD intent, roadmap items, or product discussions into implementation-ready capability plans exposing constraints, invariants, interfaces, and unresolved decisions before multi-service work.

ecc

Stats

LanguagePython

Parent stars0

MaintenanceGood

Last CommitMay 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Chunk

Overview

Workflow

Classify the request path.

Use UI path for org setup, model-provider onboarding, fix buttons, or environment selection in the CircleCI app.
Use CLI path for terminal-based project setup, validation hooks, prompt/context generation, sandbox operations, or scripted task execution.
Use mixed path when users want UI setup plus CLI execution in the same flow.

Gather minimum context.

Confirm repository/project, branch, and whether GitHub integration is in place.
Confirm whether the user is using CircleCI-managed model provider or bring-your-own keys.
For CLI operations, confirm local OS compatibility and required tokens/auth.

Execute using the matching reference.

For UI/setup flows, load chunk-ui.md.
For CLI flows, load chunk-cli.md.

Close with verification.

State what was configured or run, what remains blocked, and the next safest command or UI action.

Guardrails

Treat Chunk features as beta unless the user confirms otherwise.
Never expose or log secret values (API keys, tokens, bearer credentials).
Do not invent chunk subcommands or flags; stick to documented command families.
If sandbox features are requested, call out private preview status and any access gate.
If a task depends on org-level prerequisites (GitHub App install, org toggles, contexts), verify those first.

Reference Map

chunk-ui.md: CircleCI app setup, provider onboarding, fix buttons, environment file/setup, and operational troubleshooting.
chunk-cli.md: Installation, command map, quick-start flows, auth/env variables, and platform constraints.

Output Contract

Provide:

Path chosen (UI, CLI, or mixed) and why.
Steps executed with exact command/UI actions.
Required prerequisites not yet met.
Concrete next action to finish the user’s goal.