chunk

Savant verdict: Analyzed

Scanned or evaluated by Savant; not yet both passing.

Live evaluation

3 pass · 3 investigate · 3 fail across 9 cases. Jev accepted 9 of 10 LLM-drafted cases. Drafted and run by nvidia/nemotron-3-super-120b-a12b, validated and scored by jev-latest.

• I want to set up Chunk for my organization in CircleCI so I can use AI-assisted CI/CD. My GitHub App is already installed and I plan to use CircleCI-managed model provider.positive case · pass
• I need to troubleshoot a failing build in my CircleCI pipeline. I see a 'Fix error' button on the failed step output and want to use Chunk to get AI-assisted fixes.positive case · pass
• I want to use chunk-cli to validate my local Chunk configuration before pushing changes. I'm on macOS and have GitHub CLI installed and authenticated.positive case · investigate
• I want to run a Chunk task in the cloud to fix a flaky test, but I'm not sure if I have the CircleCI token set up or if my project is linked.edge case · investigate
• I want to use the chunk sandbox to test a new dependency, but I'm on Windows and not sure if it's supported.edge case · fail
• I want to install a Chunk skill via CLI but I don't know if my organization allows Chunk tasks or if the GitHub App is installed.edge case · pass
• I want to use Chunk to deploy my application to AWS ECS using a Docker image.negative case · fail
• Can Chunk generate a complete CircleCI config.yml file from scratch for my new Go microservice?negative case · investigate

Safety (NVIDIA SkillSpector)

0 patterns found

Structure

• No license declaredConfirm you may reuse this skill before importing it into your repository.

SKILL.md

---
name: chunk
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.
---

# 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

1. 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.
2. 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.
3. Execute using the matching reference.
- For UI/setup flows, load [chunk-ui.md](references/chunk-ui.md).
- For CLI flows, load [chunk-cli.md](references/chunk-cli.md).
4. 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](references/chunk-ui.md): CircleCI app setup, provider onboarding, fix buttons, environment file/setup, and operational troubleshooting.
- [chunk-cli.md](references/chunk-cli.md): Installation, command map, quick-start flows, auth/env variables, and platform constraints.

## Output Contract

Provide:

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