Update to CircleCI

{
  "description": "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 96
    },
    {
      "relative_path": "references/chunk-cli.md",
      "size_in_bytes": 3488
    },
    {
      "relative_path": "references/chunk-ui.md",
      "size_in_bytes": 2074
    }
  ],
  "name": "chunk",
  "skill_md_contents": "---\nname: chunk\ndescription: 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.\n---\n\n# Chunk\n\n## Overview\n\nUse 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.\n\n## Workflow\n\n1. Classify the request path.\n- Use UI path for org setup, model-provider onboarding, fix buttons, or environment selection in the CircleCI app.\n- Use CLI path for terminal-based project setup, validation hooks, prompt/context generation, sandbox operations, or scripted task execution.\n- Use mixed path when users want UI setup plus CLI execution in the same flow.\n2. Gather minimum context.\n- Confirm repository/project, branch, and whether GitHub integration is in place.\n- Confirm whether the user is using CircleCI-managed model provider or bring-your-own keys.\n- For CLI operations, confirm local OS compatibility and required tokens/auth.\n3. Execute using the matching reference.\n- For UI/setup flows, load [chunk-ui.md](references/chunk-ui.md).\n- For CLI flows, load [chunk-cli.md](references/chunk-cli.md).\n4. Close with verification.\n- State what was configured or run, what remains blocked, and the next safest command or UI action.\n\n## Guardrails\n\n- Treat Chunk features as beta unless the user confirms otherwise.\n- Never expose or log secret values (API keys, tokens, bearer credentials).\n- Do not invent `chunk` subcommands or flags; stick to documented command families.\n- If sandbox features are requested, call out private preview status and any access gate.\n- If a task depends on org-level prerequisites (GitHub App install, org toggles, contexts), verify those first.\n\n## Reference Map\n\n- [chunk-ui.md](references/chunk-ui.md): CircleCI app setup, provider onboarding, fix buttons, environment file/setup, and operational troubleshooting.\n- [chunk-cli.md](references/chunk-cli.md): Installation, command map, quick-start flows, auth/env variables, and platform constraints.\n\n## Output Contract\n\nProvide:\n\n1. Path chosen (UI, CLI, or mixed) and why.\n2. Steps executed with exact command/UI actions.\n3. Required prerequisites not yet met.\n4. Concrete next action to finish the user’s goal.\n"
}