Perplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing.
Install Dakota Factory
$ npx skills add projectbluefin/dakota --skill dakota-factory -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install projectbluefin/dakota dakota-factory --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dakota-factory .claude/skills/dakota-factory && rm -rf skills-srcUse ~/.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/
Install the "dakota-factory" agent skill from https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factory into .claude/skills/dakota-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dakota-factory", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factoryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add projectbluefin/dakota --skill dakota-factory -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install projectbluefin/dakota dakota-factory --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dakota-factory .agents/skills/dakota-factory && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dakota-factory" agent skill from https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factory into .agents/skills/dakota-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dakota-factory", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add projectbluefin/dakota --skill dakota-factory -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install projectbluefin/dakota dakota-factory --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dakota-factory .cursor/skills/dakota-factory && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dakota-factory" agent skill from https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factory into .cursor/skills/dakota-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dakota-factory", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/projectbluefin/dakota.git --path .agents/skills/dakota-factory--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add projectbluefin/dakota --skill dakota-factory -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install projectbluefin/dakota dakota-factory --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dakota-factory .gemini/skills/dakota-factory && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dakota-factory" agent skill from https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factory into .gemini/skills/dakota-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dakota-factory", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install projectbluefin/dakota dakota-factoryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add projectbluefin/dakota --skill dakota-factory -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dakota-factory .github/skills/dakota-factory && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dakota-factory" agent skill from https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factory into .github/skills/dakota-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dakota-factory", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add projectbluefin/dakota --skill dakota-factory -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install projectbluefin/dakota dakota-factory --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/projectbluefin/dakota.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dakota-factory .opencode/skills/dakota-factory && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dakota-factory" agent skill from https://github.com/projectbluefin/dakota/tree/testing/.agents/skills/dakota-factory into .opencode/skills/dakota-factory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dakota-factory", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dakota-factory- GitHub stars
- 180
- Token cost
- ~1.1k tokens
- SKILL.md length
- 511 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing.
- Works in 5 steps: Check Relevance and Authority: Identify… → Docs Are the Model → Audit Skill Usability → …
- Auditing skills
- SKILL.md covers When to Use, When NOT to Use, Core Process and Invariants, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dakota Factory is an agent skill from projectbluefin/dakota. Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing. Use when auditing skills or correcting durable guidance revealed by a task.
Its SKILL.md is about 1.1k 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 Research & Science, covering Fact-checking and source verification. The repository describes itself as: The buildstream for making Bluefin. The licence is MIT.
When your agent uses it
- Auditing skills
- Correcting durable guidance revealed by a task
Example prompts
- “/dakota-factory”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Check Relevance and Authority: Identify durable errors or missing constraints relevant to the task. Correct existing guidance when edits…
- Docs Are the Model
- Audit Skill Usability
- Verify Official Documentation
- Keep Changes Scoped: Include relevant documentation corrections with the code diff for review. Do not add unrelated writebacks, create a…
What it can do on your machine
Read from SKILL.md and the folder at commit bd5d913. 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
No scripts in the folder and no shell commands in SKILL.md.
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 Factory loads about 1.1k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 511 words of instructions outside code blocks.
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 bd5d913, republished under its MIT licence (© projectbluefin). 511 words, ~1,093 tokens.
Download SKILL.mdSave it as
.claude/skills/dakota-factory/SKILL.md (or your agent's skills folder).- name
- dakota-factory
- description
- Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing. Use when auditing skills or correcting durable guidance revealed by a task.
Dakota Factory Model
Keep documentation aligned with executable configuration. Correct durable guidance relevant to the task, without requiring a documentation change for every session.
When to Use
- Ending any implementation, debugging, or triage session that revealed non-obvious behavior or traps
- Creating, auditing, or refactoring skills in
.agents/skills/ - Updating architectural docs in
docs/to reflect running truth - Verifying library or CLI syntax against current official documentation
When NOT to Use
- Read-only queries without authorization to change documentation
- Pure dependency version updates handled automatically by Renovate
Core Process
- Check Relevance and Authority: Identify durable errors or missing constraints relevant to the task. Correct existing guidance when edits are authorized; otherwise report the finding without writing files.
- Docs Are the Model:
- Skill files are evergreen procedures, not historical logs, ledgers, or backlogs.
- Do not record session dates (e.g.
2026-08-01: we found X). Extract the timeless rule. - Do not maintain running issue tables or resolved checklists in skills. Gaps belong in GitHub issues; resolved items belong in git history.
- Audit Skill Usability:
Ensure the affected skill in
.agents/skills/contains:- Valid YAML frontmatter with
nameand a descriptivedescription; optional metadata should identify real sources, not unavailable tool requirements ## When to Use## When NOT to Use## Core Process## Invariants/## Rules## Common Rationalizations## Red Flags## Verification
- Valid YAML frontmatter with
- Verify Official Documentation:
- Identify the external tool and the version used by Dakota.
- Read its current official documentation directly, or use Context7 when available.
- Verify the specific syntax or behavior against the pinned source when needed.
- Cite the official URL in relevant guidance or optional
metadata.verified-sources.
- Keep Changes Scoped: Include relevant documentation corrections with the code diff for review. Do not add unrelated writebacks, create a commit, or publish a PR without authorization.
Show full SKILL.md (223 more words)Show less
Invariants
- Task Boundary: Documentation changes must be useful, relevant, and authorized. A read-only task can end with findings alone.
- Evergreen Truth: Workflows, elements, the Justfile, and tests are authoritative truth. Prose that disagrees with executable configuration is stale and must be excised.
- Zero Writing to
ublue-os/*: Absolute prohibition. Ask a human to report upstream manually. - Commit Trailer: Use
Assisted-by:, neverCo-authored-by:.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "Every task needs a documentation diff." | Update guidance when the task changes or corrects it; do not manufacture unrelated work. |
| "Recording the incident date gives good context." | Dated incident logs turn documentation into an unmaintained changelog. Document the timeless failure mode and prevention rule instead. |
| "I know how this CLI tool works from memory." | Verify current syntax in official documentation. Context7 is an optional retrieval tool, not a prerequisite. |
Red Flags
- Sections titled
## Lessons Learnedwith dated entries (2026-07-30: ...) - Running issue tables with live issue numbers inside skill files
- Skills lacking
## Red Flagsor## Verificationsections - Contradictions between
docs/and executable workflow YAML orJustfile
Verification
- Documentation changes are task-relevant and authorized
- No dated session logs or resolved checkmarks added to evergreen docs
- External tool syntax is verified against official sources and cited where relevant
- Skill frontmatter parses, referenced paths exist, and commands match available tooling
- All commits use conventional format 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-factory of projectbluefin/dakota.
Open the folder on GitHubat commit bd5d913
Compare with similar skills
Dakota Factory 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dakota Factory this skillprojectbluefin/dakota | 180 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Perplexity Web Searchdavila7/claude-code-templates | 33k | 11 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Citation Verification GuideGalaxy-Dawn/claude-scholar | 5.7k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Article Fact Checkerdigoal/blog | 8.6k | — | ~939 | Automated safety check: Pass | GPL-2.0 | |
| Deep Research Agent TeamImbad0202/academic-research-skills | 51k | — | ~13k | Automated safety check: Pass | Custom licence | |
| Docs Grounding Verifiermicrosoft/apm | 4k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Citation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
Article Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Deep Research Agent Team
Imbad0202/academic-research-skills
Runs a 13-agent pipeline for rigorous academic research, from forming the question through systematic search, synthesis, bias checks and an APA 7.0 report.
- Official
Docs Grounding Verifier
microsoft/apm
A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.
Fact Checking
bradygaster/squad
Review and validate claims using counter-hypothesis testing.
More from projectbluefin/dakota
All 10 skills in this repoDakota Buildstream
projectbluefin/dakota
BuildStream elements, junctions, patches, dependency graphs, and build failures in Dakota.
Dakota Extensions
projectbluefin/dakota
Package, update, and configure GNOME Shell extensions, Quick Settings panels, and schemas in Dakota.
Dakota Packaging
projectbluefin/dakota
Add, remove, or update native software built from source in Dakota, including Go, Rust, Zig, C/Meson, and binary releases.
Dakota Ujust
projectbluefin/dakota
Author safe end-user ujust recipes in files/just-overrides/default.just, including quoting, gum, JSON, and public-post confirmation.
Dakota Image
projectbluefin/dakota
OCI layer assembly, boot testing, installer boundaries, VM work, and local OTA verification for Dakota images.
Dakota Workstation
projectbluefin/dakota
Dakota host Homebrew integration and workstation-specific services.
Related
Categories
Questions about Dakota Factory
What does Dakota Factory do?
Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing. Dakota Factory is an agent skill from projectbluefin/dakota. Maintain task-relevant Dakota guidance: documentation accuracy, official-source verification, and skill auditing.
When should I use Dakota Factory?
Dakota Factory fits situations like: auditing skills; correcting durable guidance revealed by a task.
How do I install Dakota Factory in Claude Code?
Run `npx skills add projectbluefin/dakota --skill dakota-factory -a claude-code`. Or copy the skill folder (.agents/skills/dakota-factory in projectbluefin/dakota) into .claude/skills/dakota-factory in your project. Claude Code loads it when a task matches its description.
How do I install Dakota Factory in Codex?
Run `npx skills add projectbluefin/dakota --skill dakota-factory -a codex`. Or copy the skill folder (.agents/skills/dakota-factory in projectbluefin/dakota) into .agents/skills/dakota-factory in your project. Codex loads it when a task matches its description.
Can I use Dakota Factory 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-factory -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-factory, .gemini/skills/dakota-factory, .github/skills/dakota-factory and .opencode/skills/dakota-factory in your project.
What does Dakota Factory need to run?
SKILL.md names no scripts, command-line tools or credentials: Dakota Factory is instructions for the agent only.
Does Dakota Factory 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 Factory 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 Factory use?
Dakota Factory 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 Factory use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Factory?
Skills that share tags, products or a category with Dakota Factory: Perplexity Web Search (davila7/claude-code-templates, 33k stars), Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars) and Deep Research Agent Team (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dakota Factory?
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 11, 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.