Loading...
Loading...
Interactive onboarding for new AgentOps users. Guided RPI cycle on your actual codebase in under 10 minutes. Triggers: "quickstart", "get started", "onboarding", "how do I start".
npx skill4agent add boshu2/agentops quickstartPurpose: Walk a new user through their first Research-Plan-Implement cycle on their actual codebase. Under 10 minutes to first value.
references/getting-started.mdreferences/troubleshooting.md# 1. Git repo check
if git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
echo "GIT_REPO=true"
else
echo "GIT_REPO=false"
echo "Not a git repo. Some features (recent changes, vibe) need git."
echo "Options: run 'git init' to enable full features, or continue in manual mode."
fi
# 2. ao CLI availability
if command -v ao &>/dev/null; then
echo "AO_CLI=true"
ao status 2>/dev/null | head -3
else
echo "AO_CLI=false — optional, enables persistent knowledge flywheel"
fi
# 3. .agents/ directory
if [ -d ".agents" ]; then
echo "AGENTS_DIR=exists"
elif mkdir -p .agents 2>/dev/null; then
echo "AGENTS_DIR=created"
rmdir .agents 2>/dev/null # clean up test dir
else
echo "AGENTS_DIR=no_write — cannot create .agents/ directory (check permissions)"
fi
# 4. Claude Code version (informational)
claude --version 2>/dev/null || echo "Claude Code version: unknown"# Detect language/framework (monorepo-friendly)
# - Uses a shallow scan to avoid walking giant repos
# - Prints the path that triggered detection (helps when you're in the wrong subdir)
ROOT="."
GIT_ROOT=""
if git rev-parse --show-toplevel >/dev/null 2>&1; then
GIT_ROOT="$(git rev-parse --show-toplevel)"
ROOT="$GIT_ROOT"
fi
# Pretty-print paths relative to repo root when possible.
relpath() {
local p="$1"
if [[ -n "$GIT_ROOT" ]]; then
echo "${p#"$GIT_ROOT"/}"
return
fi
echo "${p#./}"
}
find_first() {
# Usage: find_first <name-pattern> (e.g., "go.mod" or "*.py")
find "$ROOT" -maxdepth 4 \
-type d \( -name .git -o -name .agents -o -name .beads -o -name node_modules \) -prune \
-o -type f -name "$1" -print -quit 2>/dev/null
}
python="$(find_first pyproject.toml)"
[[ -n "$python" ]] || python="$(find_first requirements.txt)"
[[ -n "$python" ]] || python="$(find_first setup.py)"
[[ -n "$python" ]] || python="$(find_first '*.py')"
[[ -n "$python" ]] && echo "Python detected ($(relpath "$python"))"
go="$(find_first go.mod)"
[[ -n "$go" ]] || go="$(find_first '*.go')"
[[ -n "$go" ]] && echo "Go detected ($(relpath "$go"))"
ts="$(find_first tsconfig.json)"
[[ -n "$ts" ]] || ts="$(find_first package.json)"
[[ -n "$ts" ]] || ts="$(find_first '*.ts')"
[[ -n "$ts" ]] || ts="$(find_first '*.tsx')"
[[ -n "$ts" ]] && echo "TypeScript detected ($(relpath "$ts"))"
rust="$(find_first Cargo.toml)"
[[ -n "$rust" ]] || rust="$(find_first '*.rs')"
[[ -n "$rust" ]] && echo "Rust detected ($(relpath "$rust"))"
java="$(find_first pom.xml)"
[[ -n "$java" ]] || java="$(find_first build.gradle)"
[[ -n "$java" ]] || java="$(find_first '*.java')"
[[ -n "$java" ]] && echo "Java detected ($(relpath "$java"))"
infra="$(find_first Dockerfile)"
[[ -n "$infra" ]] || infra="$(find_first Makefile)"
[[ -n "$infra" ]] || infra="$(find_first '*.sh')"
[[ -n "$infra" ]] && echo "Shell/Infra detected ($(relpath "$infra"))"# Check git state (skip if GIT_REPO=false)
git log --oneline -5 2>/dev/null
git diff --stat HEAD~3 2>/dev/null | tail -5
# Check for existing AgentOps setup
ls .agents/ 2>/dev/null && echo "AgentOps artifacts found"
ls .beads/ 2>/dev/null && echo "Beads issue tracking found"
# Repo-specific instructions (optional but high-signal)
test -f AGENTS.md && echo "AGENTS.md found (repo-specific workflow)"Welcome to AgentOps! Here are the 3 skills that matter most:
/research — Deep dive into your codebase to understand it
/plan — Break a goal into trackable issues
/vibe — Validate code before shipping
Let's do a quick tour using YOUR code.# Find what changed recently (dirty tree first; fall back to last commit if clean)
if git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
STAGED="$(git diff --name-only --cached 2>/dev/null || true)"
UNSTAGED="$(git diff --name-only 2>/dev/null || true)"
UNTRACKED="$(git ls-files --others --exclude-standard 2>/dev/null || true)"
RECENT_FILES="$(printf "%s\n%s\n%s\n" "$STAGED" "$UNSTAGED" "$UNTRACKED" | sed '/^$/d' | sort -u)"
# Clean repo: fall back to last commit, then fall back to "some tracked files"
if [[ -z "$RECENT_FILES" ]] && git rev-parse --verify HEAD >/dev/null 2>&1; then
RECENT_FILES="$(git show --name-only --pretty="" HEAD 2>/dev/null | sed '/^$/d')"
fi
[[ -z "$RECENT_FILES" ]] && RECENT_FILES="$(git ls-files 2>/dev/null | head -50)"
# Best-effort noise filtering; keep unfiltered list if filtering drops everything
FILTERED="$(echo "$RECENT_FILES" | grep -Ev '^(\\.agents/|cli/\\.agents/|\\.beads/)' || true)"
[[ -n "$FILTERED" ]] && RECENT_FILES="$FILTERED"
echo "$RECENT_FILES" | head -10
else
echo "Not a git repo; skipping recent-change detection."
fi/researchBased on what I found, here's a task we could plan:
"<specific improvement based on what was found>"
This is what /plan does — decomposes goals into trackable issues with
dependencies and waves.# Use the same RECENT_FILES list from Step 3.
# If you didn't run Step 3 in the same shell, re-run the Step 3 snippet to rebuild RECENT_FILES.
if [[ -n "${RECENT_FILES:-}" ]]; then
echo "$RECENT_FILES" | head -10
else
echo "RECENT_FILES is empty; re-run the Step 3 snippet to rebuild it."
fi/council --quick/vibeYou've just completed a mini RPI cycle:
Research → Plan → Validate
Here's what else is available:
IMPLEMENT VALIDATE COLLABORATE
/implement - execute task /vibe - code check /council - multi-model review
/crank - run full epic /pre-mortem - plan check /swarm - parallel agents
/plan - decompose work /post-mortem - wrap up /handoff - session handoff
EXPLORE TRACK
/research - deep dive /knowledge - query learnings
/bug-hunt - investigate /inbox - agent messages
/complexity - code metrics /trace - decision history
/doc - generate docs /retro - extract learnings| State | Suggestion |
|---|---|
| Recent commits, no tests | "Try |
| Open issues/TODOs | "Try |
| Complex codebase, new to it | "Try |
| Bug reports or failures | "Try |
| Clean state, looking for work | "Try |
# Gather state from pre-flight (Step 0)
command -v ao &>/dev/null && AO_AVAILABLE=true || AO_AVAILABLE=false
command -v bd &>/dev/null && BD_AVAILABLE=true || BD_AVAILABLE=false
command -v codex &>/dev/null && CODEX_AVAILABLE=true || CODEX_AVAILABLE=false
ls .agents/ &>/dev/null && AGENTS_DIR=true || AGENTS_DIR=false
ls .beads/ &>/dev/null && BEADS_DIR=true || BEADS_DIR=false
git rev-parse --is-inside-work-tree &>/dev/null && GIT_REPO=true || GIT_REPO=false| Current State | Tier | Next Step |
|---|---|---|
| No git repo | — | "Initialize git with |
Git repo, no | Tier 0 | "You're at Tier 0 — skills work standalone. When you want learnings to persist across sessions, install the |
| Tier 0+ | "Run |
| Tier 1 | "Knowledge flywheel is active. When you have multi-issue epics, add beads for issue tracking: |
| Tier 2 | "Full RPI stack. Start with repo instructions (check |
| Tier 2+ | "Full stack with cross-vendor. Try |
skills/vibe/SKILL.mdskills/research/SKILL.mdskills/plan/SKILL.md