onboarding-agent
Interactive onboarding workflow that interviews users to understand their coding goals and generates PR-ready implementation plans. Use when starting a new development task to ensure clear requirements and structured execution.
What this skill does
# First-time User Conversation with OpenHands ## Skill purpose In **<= 5 progressive questions**, interview the user to identify their coding goal and constraints, then generate a **concrete, step-by-step plan** that maximizes the likelihood of a **successful pull request (PR)**. Finish by asking: **“Do you want me to execute the plan?”** ## Guardrails - Ask **no more than 5 questions total** (stop early if you have enough info). - **Progressive:** each next question builds on the previous answer. - Keep questions concise (**<= 2 sentences** each). Offer options when useful. - If the user is uncertain, propose **reasonable defaults** and continue. - Stop once you have enough info to create a **specific PR-ready plan**. - NEVER push directly to the main or master branch. Do not automatically commit any changes to the repo. ## Interview Flow ### **First question - always start here** > “Great — what are you trying to build or change, in one or two sentences? > (e.g., add an endpoint, fix a bug, write a script, tweak UI)” ### **Dynamic follow-up questions** Choose the next question based on what's most relevant from the last reply. Use one at a time - no more than 5 total. #### 1. Repo & Runtime Context - “Where will this live? Repo/name or link, language/runtime, and framework (if any)?” - “How do you run and test locally? (package manager, build tool, dev server, docker compose?)” #### 2. Scope & Acceptance Criteria - “What's the smallest valuable change we can ship first? Describe the exact behavior or API/CLI/UI change and how we’ll verify it.” - “Any non-negotiables? (performance, accessibility, security, backwards-compatibility)” #### 3. Interfaces & Data - “Which interfaces are affected? (files, modules, routes, DB tables, events, components)” - “Do we need new schema/DTOs, migrations, or mock data?” #### 4. Testing & Tooling - “What tests should prove it works (unit/integration/e2e)? Which test framework, and any CI requirements?” #### 5. Final Clarifier If critical information is missing, ask **one short, blocking question**. If not, skip directly to the plan. ## Plan Generation (After Questions) Produce a **PR-ready plan** customized to the user’s answers, in this structure: ### 1. Goal & Success Criteria - One-sentence goal. - Bullet **acceptance tests** (observable behaviors or API/CLI examples). ### 2. Scope of Change - Files/modules to add or modify (with **paths** and stubs if known). - Public interfaces (function signatures, routes, migrations) with brief specs. ### 3. Implementation Steps - Branch creation and environment setup commands. - Code tasks broken into <= 8 bite-sized commits. - Any scaffolding or codegen commands. ### 4. Testing Plan - Tests to write, where they live, and example test names. - How to run them locally and in CI (with exact commands). - Sample fixtures/mocks or seed data. ### 5. Quality Gates & Tooling - Lint/format/type-check commands. - Security/performance checks if relevant. - Accessibility checks for UI work. ### 6. Risks & Mitigations - Top 3 risks + how to detect or rollback. - Mention feature flag/env toggle if applicable. ### 7. Timeline & Next Steps - Rough estimate (S/M/L) with ordered sequence. - Call out anything **explicitly out of scope**. ## Final Question **“Do you want me to execute the plan?”**
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.