skill-nix-research
- Repo stars 435
- Author updated Live
- Author repo nvim
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @benbrastmckie · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-nix-research
description: Conduct Nix/NixOS/Home Manager research using MCP-NixOS, web docs, and codebase exploration. Inv…
category: documentation
runtime: no special runtime
---
# skill-nix-research output preview
## PART A: Task fit
- Use case: Conduct Nix/NixOS/Home Manager research using MCP-NixOS, web docs, and codebase exploration. Invoke for nix research tasks. Thin wrapper that delegates Nix research to nix-research-agent subagent. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Context References / Trigger Conditions / Execution Flow” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Conduct Nix/NixOS/Home Manager research using MCP-NixOS, web docs, and codebase exploration. Invoke for nix research tasks. Thin wrapper that delegates Nix research to nix-research-agent subagent. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Context References / Trigger Conditions / Execution Flow” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Context References / Trigger Conditions / Execution Flow”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-nix-research
description: Conduct Nix/NixOS/Home Manager research using MCP-NixOS, web docs, and codebase exploration. Inv…
category: documentation
source: benbrastmckie/nvim
---
# skill-nix-research
## When to use
- Conduct Nix/NixOS/Home Manager research using MCP-NixOS, web docs, and codebase exploration. Invoke for nix research t…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Context References / Trigger Conditions / Execution Flow” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-nix-research" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Context References / Trigger Conditions / Execution Flow
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Nix Research Skill
Thin wrapper that delegates Nix research to nix-research-agent subagent.
IMPORTANT: This skill implements the skill-internal postflight pattern. After the subagent returns, this skill handles all postflight operations (status update, artifact linking, git commit) before returning.
Context References
Reference (do not load eagerly):
- Path:
.opencode/context/core/formats/return-metadata-file.md- Metadata file schema - Path:
.opencode/context/core/patterns/postflight-control.md- Marker file protocol - Path:
.opencode/context/core/patterns/jq-escaping-workarounds.md- jq escaping patterns
Trigger Conditions
This skill activates when:
- Task language is "nix"
- Research is needed for Nix, NixOS, or Home Manager configuration
- Package definitions or module patterns need to be gathered
Execution Flow
Stage 1: Input Validation
Validate required inputs:
task_number- Must be provided and exist in state.jsonfocus_prompt- Optional focus for research direction
# Lookup task
task_data=$(jq -r --argjson num "$task_number" \
'.active_projects[] | select(.project_number == $num)' \
specs/state.json)
# Validate exists
if [ -z "$task_data" ]; then
return error "Task $task_number not found"
fi
# Extract fields
language=$(echo "$task_data" | jq -r '.language // "nix"')
status=$(echo "$task_data" | jq -r '.status')
project_name=$(echo "$task_data" | jq -r '.project_name')
description=$(echo "$task_data" | jq -r '.description // ""')
Stage 2: Preflight Status Update
Update task status to "researching" BEFORE invoking subagent.
bash .opencode/scripts/update-task-status.sh preflight "$task_number" research "$session_id"
Stage 3: Create Postflight Marker
mkdir -p "specs/OC_${padded_num}_${project_name}"
cat > "specs/OC_${padded_num}_${project_name}/.postflight-pending" << EOF
{
"session_id": "${session_id}",
"skill": "skill-nix-research",
"task_number": ${task_number},
"operation": "research",
"reason": "Postflight pending: status update, artifact linking, git commit",
"created": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
}
EOF
Stage 4: Prepare Delegation Context
{
"session_id": "sess_{timestamp}_{random}",
"delegation_depth": 1,
"delegation_path": ["orchestrator", "research", "skill-nix-research"],
"timeout": 3600,
"task_context": {
"task_number": N,
"task_name": "{project_name}",
"description": "{description}",
"language": "nix"
},
"focus_prompt": "{optional focus}",
"metadata_file_path": "specs/OC_{NNN}_{SLUG}/.return-meta.json"
}
Stage 5: Invoke Subagent
CRITICAL: You MUST use the Task tool to spawn the subagent.
Tool: Task (NOT Skill)
Parameters:
- subagent_type: "nix-research-agent"
- prompt: [Include task_context, delegation_context, focus_prompt, metadata_file_path]
- description: "Execute Nix research for task {N}"
The subagent will:
- Search local Nix configuration using Read, Grep, Glob
- Search web for NixOS/Home Manager documentation
- Query MCP-NixOS for package/option information (if available)
- Analyze findings and synthesize recommendations
- Create research report
- Write metadata file
- Return brief text summary
Stage 6: Parse Subagent Return
metadata_file="specs/OC_${padded_num}_${project_name}/.return-meta.json"
if [ -f "$metadata_file" ] && jq empty "$metadata_file" 2>/dev/null; then
status=$(jq -r '.status' "$metadata_file")
artifact_path=$(jq -r '.artifacts[0].path // ""' "$metadata_file")
artifact_type=$(jq -r '.artifacts[0].type // ""' "$metadata_file")
artifact_summary=$(jq -r '.artifacts[0].summary // ""' "$metadata_file")
else
status="failed"
fi
Stage 7: Update Task Status (Postflight)
If status is "researched", update state.json and TODO.md.
bash .opencode/scripts/update-task-status.sh postflight "$task_number" research "$session_id"
Stage 8: Link Artifacts
Add artifact to state.json with summary.
Stage 9: Git Commit
git add -A
git commit -m "task ${task_number}: complete research
Session: ${session_id}
Stage 10: Cleanup
rm -f "specs/OC_${padded_num}_${project_name}/.postflight-pending"
rm -f "specs/OC_${padded_num}_${project_name}/.return-meta.json"
Stage 11: Return Brief Summary
Research completed for task {N}:
- Found NixOS module patterns
- Identified package configuration
- Created report at specs/{NNN}_{SLUG}/reports/research-{NNN}.md
- Status updated to [RESEARCHED]
- Changes committed
Error Handling
Input Validation Errors
Return immediately if task not found.
Metadata File Missing
Keep status as "researching" for resume.
Git Commit Failure
Non-blocking: Log failure but continue.
Return Format
Brief text summary (NOT JSON).
Decide Fit First
Design Intent
How To Use It
Boundaries And Review