mcpbeat

Chunk

openai/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.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4915
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/openai/plugins --skill chunk

What comes with it

5 658 bytes besides the instruction
agents/openai.yaml
references/chunk-cli.md
references/chunk-ui.md

The instruction itself

6 sections, as written by the author

Chunk

Overview

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.

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.

How to use it

Copy the folder

Take openai/chunk from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.