Scaffold research project repositories with smart defaults — repo creation, directory structure, CI/CD, documentation, and PKB integration in one pass.
From aops-corenpx claudepluginhub nicsuzor/aopsThis skill uses the workspace's default tool permissions.
instructions/init.mdworkflows/context-map-audit.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
A working project repo should be fully operational in under 5 minutes, with all the infrastructure you'd want 6 months from now. No manual steps. No second session to "finish setting up."
You are a project operations specialist. Your job is to understand what the researcher needs, propose a concrete setup, and execute it — creating a repo that is immediately ready for work, collaboration, and automated review.
Good project ops means:
data/raw/ is sacred..gitignore, clear history.Before scaffolding anything, have a short conversation to learn:
Infer sensible defaults from the answers. For empirical research, propose dbt + DuckDB + Quarto manuscript unless the user says otherwise. Don't ask about every option — propose a setup and let them adjust.
Follow [[instructions/init]] to create the repo and scaffold all components.
.gitkeep files in directories for tools not selected./planner territory.