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 Buildstream

by projectbluefin in projectbluefin/dakota

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

MITAuto-check passed

Install Dakota Buildstream

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

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

GitHub CLI
$ gh skill install projectbluefin/dakota dakota-buildstream --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-buildstream .claude/skills/dakota-buildstream && 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-buildstream
GitHub stars
180
Token cost
~1k tokens
SKILL.md length
451 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 6 steps: Inspect Graph: Run just bst show --deps… → Consult Nearest Pattern: Check elements… → Verify Syntax: Check syntax against… → …
  • Editing elements
  • SKILL.md covers When to Use, When NOT to Use, Core Process and Invariants, plus 4 more sections
  • Calls just, python3 and pip

What it does

Dakota Buildstream is an agent skill from projectbluefin/dakota. BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota. Use when editing elements, project.conf, junctions, or patches.

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

The repository describes itself as: The buildstream for making Bluefin. The licence is MIT.

When your agent uses it

  • Editing elements

Example prompts

  • “/dakota-buildstream”

Requirements

  • Python 3

Workflow steps

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

  1. Inspect Graph: Run just bst show --deps all to trace dependencies and dependents.
  2. Consult Nearest Pattern: Check elements with similar build systems (manual, autotools, meson, cmake).
  3. Verify Syntax: Check syntax against official BuildStream documentation (/apache/buildstream).
  4. Implement Deterministically: Ensure build/install steps are reproducible (no network, timestamps, or host identity).
  5. Validate Graph: Run just validate. For element-specific tests, build the narrowest target (just bst build ).
  6. Patch Hygiene: For junction patches, update patches/, verify with just patch-drift-check, and set Upstream-Status: headers.

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
    • python3
    • pip

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

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    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 Buildstream loads about 1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 451 words of instructions outside code blocks.

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

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). 451 words, ~1,037 tokens.

Download SKILL.mdSave it as .claude/skills/dakota-buildstream/SKILL.md (or your agent's skills folder).
name
dakota-buildstream
description
BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota. Use when editing elements, project.conf, junctions, or patches.
metadata.context7-sources
/apache/buildstream

Dakota BuildStream

Dakota builds the bootc desktop image entirely from source using BuildStream 2. Never translate RPM, DNF, COPR, or Containerfile workflows into this repository.

When to Use

  • Creating, editing, or removing .bst elements in elements/
  • Modifying project.conf or junction configurations (elements/gnome-build-meta.bst, elements/freedesktop-sdk.bst)
  • Managing downstream patches in patches/
  • Triaging build, sandbox, or artifact cache failures in local runs or CI

When NOT to Use

  • Workstation Homebrew integration → load dakota-workstation
  • End-user ujust recipes → load dakota-ujust
  • GNOME Shell extensions packaging → load dakota-extensions
  • Image layer composition and boot verification → load dakota-image

Core Process

  1. Inspect Graph: Run just bst show --deps all <element> to trace dependencies and dependents.
  2. Consult Nearest Pattern: Check elements with similar build systems (manual, autotools, meson, cmake).
  3. Verify Syntax: Check syntax against official BuildStream documentation (/apache/buildstream).
  4. Implement Deterministically: Ensure build/install steps are reproducible (no network, timestamps, or host identity).
  5. Validate Graph: Run just validate. For element-specific tests, build the narrowest target (just bst build <element>).
  6. Patch Hygiene: For junction patches, update patches/, verify with just patch-drift-check, and set Upstream-Status: headers.

Invariants

  • Compose vs Stack: kind: compose generates layer filesystem artifacts. kind: stack only aggregates dependencies and outputs zero filesystem files.
  • No Post-Install Packaging: All runtime software must be integrated via BST elements before OCI composition.
  • Junction Patches: Patch junctions via kind: patch_queue sources. Never modify .bst/staged-junctions/.
  • Source Pinning: Pin git sources to commit SHAs or release tags. Never track mutable branches in production elements.
  • Reproducibility: No network calls, $(date), $(hostname), whoami, or random seeds in build commands.
  • Directory Creation: Run mkdir -p before creating links or writing files into target directories.
  • Generated Cargo Sources: Generate crate manifests via:
    bash
    python3 files/scripts/generate_cargo_sources.py path/to/Cargo.lock
Show full SKILL.md (177 more words)Show less

Common Rationalizations

RationalizationReality
"I can install this package with DNF in a container step."Dakota has no DNF or RPM database. All packages are BST elements.
"A kind: stack element will put its files into the image layer."Stack elements produce empty artifacts. Layers require kind: compose.
"I'll fetch dependencies during install-commands."Sandboxes lack network access during build. All sources must be declared in sources:.
"I'll patch the staged junction file directly in .bst/."Staged junction edits are wiped on cache cleans. Use patches/ with patch_queue.

Red Flags

  • rpm-ostree, dnf, apt, or pip install inside build instructions
  • Using kind: stack inside elements/oci/layers/
  • ref: pointing to a branch name instead of a git commit or tag
  • Using $(date) or $(hostname) in install commands
  • Adding patches without an Upstream-Status: header and exit condition

Verification

  • just validate passes without errors
  • just bst show --deps all <element> resolves cleanly
  • Narrowest element builds in isolation via just bst build <element>
  • just patch-drift-check passes if junction patches were touched
  • Commit message follows <type>(<scope>): <desc> with Assisted-by: trailer

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-buildstream of projectbluefin/dakota.

Open the folder on GitHubat commit 909f687

Compare with similar skills

Dakota Buildstream 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 Buildstream compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dakota Buildstream this skillprojectbluefin/dakota180—~1kAutomated safety check: PassMIT
Dependency Scanningsickn33/agentic-awesome-skills47k1 repos~2.4kAutomated safety check: PassMIT
Dependency PatchesLedgerHQ/ledger-live622—~491Automated safety check: PassMIT
Dependency Checkruvnet/ruflo74k—~258Automated safety check: PassMIT
Graphagenticnotetaking/arscontexta3.5k—~4.9kAutomated safety check: NotesMIT
Bigquery Graphgoogle/adk-python22k—~4.8kAutomated safety check: PassApache-2.0

Similar skills

  • Dependency Scanning

    sickn33/agentic-awesome-skills

    Scan package dependencies for known vulnerabilities using Snyk, Dependabot, and OWASP Dependency-Check.

    47k GitHub starsUsed in 1 repo~2.4k tokens
    SecurityAuto-check passed

  • Dependency Patches

    LedgerHQ/ledger-live

    Read before creating or changing patches/.patch, pnpm.patchedDependencies, or using pnpm patch to modify third-party dependency source.

    622 GitHub stars~491 tokensUpdated today
    Auto-check passed

  • Dependency Check

    ruvnet/ruflo

    Scan project dependencies for known vulnerabilities and CVEs.

    74k GitHub stars~258 tokensUpdated today
    SecurityAuto-check passed

  • Graph

    agenticnotetaking/arscontexta

    Interactive knowledge graph analysis. An agent skill from agenticnotetaking/arscontexta.

    3.5k GitHub stars~4.9k tokensUpdated 7 mo ago
    Knowledge ManagementAuto-check: notes

  • Bigquery Graph

    google/adk-python

    Official

    Skill for Graph Query Language (GQL) or SQL/PGQ queries against a property graph.

    22k GitHub stars~4.8k tokensUpdated today
    DatabasesAuto-check passed

  • Dependency Update

    codewhale-hq/Codewhale

    Read release notes/changelogs, update a defined dependency scope, handle breaking changes, and verify.

    41k GitHub stars~142 tokensUpdated today
    DevelopmentAuto-check passed

More from projectbluefin/dakota

All 10 skills in this repo

  • 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

  • Dakota Workstation

    projectbluefin/dakota

    Dakota host Homebrew integration and workstation-specific services.

    180 GitHub stars~937 tokensUpdated today
    Auto-check passed

Questions about Dakota Buildstream

What does Dakota Buildstream do?

BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota. Dakota Buildstream is an agent skill from projectbluefin/dakota. BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota.

When should I use Dakota Buildstream?

Dakota Buildstream fits situations like: editing elements.

How do I install Dakota Buildstream in Claude Code?

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

How do I install Dakota Buildstream in Codex?

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

Can I use Dakota Buildstream 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-buildstream -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-buildstream, .gemini/skills/dakota-buildstream, .github/skills/dakota-buildstream and .opencode/skills/dakota-buildstream in your project.

What does Dakota Buildstream need to run?

Going by SKILL.md and its folder, Dakota Buildstream needs the command-line tools its instructions call (just, python3 and pip). Our summary lists: Python 3.

Does Dakota Buildstream access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dakota Buildstream 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 Buildstream use?

Dakota Buildstream 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 Buildstream use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Buildstream?

Skills that share tags, products or a category with Dakota Buildstream: Dependency Scanning (sickn33/agentic-awesome-skills, 47k stars), Dependency Patches (LedgerHQ/ledger-live, 622 stars), Dependency Check (ruvnet/ruflo, 74k stars) and Graph (agenticnotetaking/arscontexta, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dakota Buildstream?

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.