Oskar
Community@oskarrough
https://radio4000.com/oskar
Agent Skills by Oskar
Showing 14 vetted skills indexed across 1 GitHub repositories.
oskarrougharbe-bro
Rewrites the assistant's previous reply in plain language without jargon.
oskarrougharbe-documentation
Writes and restructures user-facing documentation using the Diátaxis four-mode framework.
oskarrougharbe-changelog
Write user-facing changelog entries from development work and commit history.
oskarrougharbe-benchmark-agent-guidance
Benchmarks agent guidance changes by comparing fresh-agent runs across controlled A/B trials.
oskarrougharbe-jj-jujutsu
Guides version control operations using jj (jujutsu) instead of git commands.
oskarrougharbe-improve-codebase
Identify shallow modules across a repository and design deeper interfaces using deletion and knob tests.
oskarrougharbe-delegate
Delegates coding outcomes to worker agents in herdr panes and collects verified reports.
oskarrougharbe-mull
Runs a six-stage design workflow from clarified request to implementation plan with review gates.
oskarrougharbe-diagram-first
Draws a 5-10 line ASCII pipeline of the user's verb before writing prose or code.
oskarrougharbe-review
Reviews code diffs against spec, correctness, and quality axes or sweeps codebases to file follow-up tasks.
oskarrougharbe-pipeline-audit
Audit README pipeline diagrams against actual call paths to flag unnecessary wrapper functions.
oskarrougharbe-product-description
Drafts feature-by-feature product behavior documents from source code and verifies them against the running product.
oskarrougharbe-orchestrate
Triages backlogs and design docs into dependency-wired dispatch plans for delegated workers.
oskarrougharbe-discover-primitives
Distills an unfamiliar repository into at most 10 reusable primitives and a dependency graph.
Frequently Asked Questions About Oskar
FAQPage SchemaWhat tasks can I accomplish with Oskar's arbe skills?▼
You can run two-mode code reviews, audit pipeline diagrams against real call paths, refactor shallow modules into deep ones, write Diátaxis documentation and changelogs, run six-stage design sessions, distill repos into reusable primitives, and delegate outcomes to worker agents.
Who are these skills designed for?▼
Software engineers and technical leads who maintain codebases, author user-facing documentation, and coordinate multi-agent work. They suit anyone doing repo-wide refactoring, design planning before coding, or tuning agent guidance such as AGENTS.md files and system prompts.
How do the design and planning skills work in practice?▼
arbe-diagram-first draws a 5-10 line ASCII pipeline of the user verb and waits for agreement before any code. For bigger efforts, arbe-mull runs six stages — clarify, questions, research, design, outline, plan — with a review gate between each, stopping at the plan.
What prerequisites or dependencies do these skills require?▼
arbe-delegate requires HERDR_ENV=1 and herdr panes for worker agents. arbe-pipeline-audit requires existing diagrams, otherwise run arbe-diagram-first first. arbe-jj-jujutsu assumes jj (jujutsu) is used for version control instead of git, with explicit revisions and no staging area.
How do the skills handle version control differently from git?▼
arbe-jj-jujutsu routes all version-control commands through jj (jujutsu) instead of git. It covers the change-versus-commit distinction, the absence of a staging area, explicit revisions, and safe split and restore operations for managing code history.