New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dakota CI

by projectbluefin in projectbluefin/dakota

Diagnose or change Dakota validation, build, publish, e2e, cache, remote-execution, and architecture workflows.

MITAuto-check passedTesting & QA

Install Dakota CI

skills CLI
$ npx skills add projectbluefin/dakota --skill dakota-ci -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install projectbluefin/dakota dakota-ci --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dakota-ci .claude/skills/dakota-ci && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dakota-ci
GitHub stars
180
Token cost
~936 tokens
SKILL.md length
448 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Diagnose or change Dakota validation, build, publish, e2e, cache, remote-execution, and architecture workflows.

  • Works in 5 steps: Route the Workflow: Identify the failing… → Inspect at Run SHA: Read the workflow… → Isolate Root Cause: Distinguish… → …
  • Tasks that involve End-to-end testing
  • SKILL.md covers When to Use, When NOT to Use, Core Process and Invariants, plus 4 more sections
  • Calls just

What it does

Dakota CI is an agent skill from projectbluefin/dakota. Diagnose or change Dakota validation, build, publish, e2e, cache, remote-execution, and architecture workflows.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing. It works with GitHub Actions. The repository describes itself as: The buildstream for making Bluefin. The licence is MIT.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “/dakota-ci”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Route the Workflow: Identify the failing workflow
  2. Inspect at Run SHA: Read the workflow YAML at the exact commit that executed.
  3. Isolate Root Cause: Distinguish syntax/permission failure (zero jobs run), source fetch failure, remote CAS cache failure, or BST…
  4. Enforce Least Privilege: Ensure workflow caller permissions strictly match what reusable workflows demand.
  5. Validate Locally: Run just check-publish-workflow and just validate before submitting.

What it can do on your machine

Read from SKILL.md and the folder at commit 909f687. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • just

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dakota CI loads about 936 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 448 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~936

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from projectbluefin/dakota at commit 909f687, republished under its MIT licence (© projectbluefin). 448 words, ~936 tokens.

Download SKILL.mdSave it as .claude/skills/dakota-ci/SKILL.md (or your agent's skills folder).
name
dakota-ci
description
Diagnose or change Dakota validation, build, publish, e2e, cache, remote-execution, and architecture workflows.
metadata.context7-sources
/apache/buildstream

Dakota CI

Workflow YAML in .github/workflows/ is the current source of truth. Do not rely on historical runbooks when the workflow says something different.

When to Use

  • Modifying or debugging GitHub Actions workflows in .github/workflows/
  • Diagnosing runner startup, syntax, matrix, or permission failures
  • Changing build, publish, or validation triggers and artifact flows
  • Investigating remote CAS caching or remote execution integration

When NOT to Use

  • Stable promotion, image signing, cosign attestation, or rollback → load dakota-release
  • BST element syntax or internal build errors → load dakota-buildstream
  • Reviewing PRs and issue management → load dakota-review

Core Process

  1. Route the Workflow: Identify the failing workflow:
    • validate.yml: PR graph checks and patch drift
    • build.yml / build-aarch64.yml: Remote execution x86/ARM builds into CAS
    • publish.yml: CAS artifact checkout, squashing, tagging, signing
    • e2e.yml: Manual testsuite dispatch against published images
  2. Inspect at Run SHA: Read the workflow YAML at the exact commit that executed.
  3. Isolate Root Cause: Distinguish syntax/permission failure (zero jobs run), source fetch failure, remote CAS cache failure, or BST compilation error.
  4. Enforce Least Privilege: Ensure workflow caller permissions strictly match what reusable workflows demand.
  5. Validate Locally: Run just check-publish-workflow and just validate before submitting.

Invariants

  • Third-Party Actions: Pin all third-party actions to full 40-character commit SHAs with an inline version comment. projectbluefin/actions@v1 is an intentional managed-tag exception.
  • Build vs Publish Separation: build.yml writes artifacts to the remote CAS; publish.yml only exports artifacts already present in the CAS for that exact resolved SHA.
  • e2e Workflow Gate: e2e.yml runs only via workflow_dispatch against an already-published tag. It does not gate PRs.
  • Atomic Matrices: Do not cancel or serialize matrix siblings (default, nvidia, gaming, nvidia-gaming) without explicit human approval.
  • Truth in Reporting: Never report CI as green while workflows are pending, queued, or skipped.
Show full SKILL.md (161 more words)Show less

Common Rationalizations

RationalizationReality
"I will add e2e.yml to PR checks so we catch regressions earlier."PRs do not push images to GHCR. Running e2e on a PR tests a stale public tag, not the PR.
"A commit SHA is overkill; a version tag like @v2 is fine."Tags are mutable. Security policy requires 40-character commit SHAs for third-party actions.
"CI is basically green, only one matrix variant is still running."All matrix siblings must complete. Partial runs leave broken variant pairs.

Red Flags

  • Unpinned third-party actions (using @v1, @main instead of SHA)
  • Adding e2e.yml as a required pull-request status check
  • Modifying release gates or promotion steps in build.yml or publish.yml
  • Asserting CI passed when checks are still in progress

Verification

  • just check-publish-workflow passes
  • just test-render-card passes
  • All modified workflow files pass YAML linting and schema validation
  • Third-party actions are pinned to full commit SHAs with version comments
  • PR description specifies local checks run vs CI status

References

© projectbluefin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/dakota-ci of projectbluefin/dakota.

Open the folder on GitHubat commit 909f687

Compare with similar skills

Dakota CI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dakota CI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dakota CI this skillprojectbluefin/dakota180—~936Automated safety check: PassMIT
RStudio Selenium to Playwright Migrationrstudio/rstudio5.1k—~3.6kAutomated safety check: PassCustom licence
Debugging Opik E2E Testscomet-ml/opik22k—~1.8kAutomated safety check: PassApache-2.0
Local CImodule-federation/core2.7k—~914Automated safety check: PassMIT
Detect Flaky Testsagent-substrate/substrate4.8k—~3kAutomated safety check: PassApache-2.0
Debug Playwrightquay/quay2.8k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • RStudio Selenium to Playwright Migration

    rstudio/rstudio

    Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.

    5.1k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check passed

  • Debugging Opik E2E Tests

    comet-ml/opik

    Investigates a failed Opik end-to-end test from CI, TestOps or a local run, decides regression versus flake, and proposes a fix without editing tests.

    22k GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Local CI

    module-federation/core

    Run this repository's local CI parity commands and pnpm run ci:local jobs.

    2.7k GitHub stars~914 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Detect Flaky Tests

    agent-substrate/substrate

    Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM…

    4.8k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

  • Debug Playwright

    quay/quay

    Debug Playwright E2E test failures from GitHub Actions CI runs.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Blockless Extension E2E

    FreakStudioCN/mpy-hardware-extension

    Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…

    154 GitHub stars~1.2k tokensUpdated 12 days ago
    Testing & QAAuto-check: notes

More from projectbluefin/dakota

All 10 skills in this repo

  • Dakota Buildstream

    projectbluefin/dakota

    BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota.

    180 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Dakota Extensions

    projectbluefin/dakota

    Package, update, and configure GNOME Shell extensions, Quick Settings panels, and schemas in Dakota.

    180 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Dakota Factory

    projectbluefin/dakota

    Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing.

    180 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Dakota Packaging

    projectbluefin/dakota

    Add, remove, or update native software built from source in Dakota, including Go, Rust, Zig, C/Meson, and binary releases.

    180 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Dakota Ujust

    projectbluefin/dakota

    Author safe end-user ujust recipes in files/just-overrides/default.just, including quoting, gum, JSON, and public-post confirmation.

    180 GitHub stars~1.1k tokensUpdated today
    Auto-check: notes

  • Dakota Image

    projectbluefin/dakota

    OCI layer assembly, boot testing, installer boundaries, VM work, and local OTA verification for Dakota images.

    180 GitHub stars~929 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Dakota CI

What does Dakota CI do?

Diagnose or change Dakota validation, build, publish, e2e, cache, remote-execution, and architecture workflows. Dakota CI is an agent skill from projectbluefin/dakota. Diagnose or change Dakota validation, build, publish, e2e, cache, remote-execution, and architecture workflows.

When should I use Dakota CI?

Dakota CI fits situations like: tasks that involve End-to-end testing.

How do I install Dakota CI in Claude Code?

Run `npx skills add projectbluefin/dakota --skill dakota-ci -a claude-code`. Or copy the skill folder (.agents/skills/dakota-ci in projectbluefin/dakota) into .claude/skills/dakota-ci in your project. Claude Code loads it when a task matches its description.

How do I install Dakota CI in Codex?

Run `npx skills add projectbluefin/dakota --skill dakota-ci -a codex`. Or copy the skill folder (.agents/skills/dakota-ci in projectbluefin/dakota) into .agents/skills/dakota-ci in your project. Codex loads it when a task matches its description.

Can I use Dakota CI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add projectbluefin/dakota --skill dakota-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dakota-ci, .gemini/skills/dakota-ci, .github/skills/dakota-ci and .opencode/skills/dakota-ci in your project.

What does Dakota CI need to run?

Going by SKILL.md and its folder, Dakota CI needs the command-line tools its instructions call (just).

Does Dakota CI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dakota CI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dakota CI use?

Dakota CI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dakota CI use?

About 936 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dakota CI?

Skills that share tags, products or a category with Dakota CI: RStudio Selenium to Playwright Migration (rstudio/rstudio, 5.1k stars), Debugging Opik E2E Tests (comet-ml/opik, 22k stars), Local CI (module-federation/core, 2.7k stars) and Detect Flaky Tests (agent-substrate/substrate, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dakota CI?

projectbluefin (a GitHub organization) maintains it in projectbluefin/dakota, which has 180 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.

Source: projectbluefin/dakota on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.