mcpField
U
user-onboarding-sop

user-onboarding-sop

github.com/igorwarzochaAgent workflows122103 installsUpdated 38w ago
Repository

About user-onboarding-sop

user-onboarding-sop is an agent skill for creating end-user-focused guidance in AGENTS.md files, complementing `/init user`. It emphasizes verified documentation, setup, usage, and troubleshooting rather than development details.

Key features

  1. 01Find verified documentation links
  2. 02Record prerequisites and installation steps
  3. 03Map commands and common usage
  4. 04Focus AGENTS.md on end-user support

Use cases

  1. 01Prepare end-user setup guidance
  2. 02Document launch commands and usage patterns
  3. 03Help users find troubleshooting resources

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/igorwarzocha/opencode-workflows --skill user-onboarding-sop

After installing, type/user-onboarding-sopin Claude Code to confirm it loaded.

Details

From the project README

User Onboarding SOP

This SOP COMPLEMENTS the /init user command by providing end-user assistance mapping for AGENTS.md files.

CRITICAL: This is for END-USER assistance ONLY.

## Phase 1: Resource Discovery 1. **Official Docs**: The agent MUST use web search for real documentation URLs. Identify Getting Started, API Ref, and Troubleshooting links. 2. **Setup**: Identify Prerequisites, Installation commands, and Environment Variables. 3. **Usage**: Identify CLI entry points, primary commands, and common usage patterns.

Phase 2: AGENTS.md Composition

Target a relaxed output length of ~100 lines. Focus on helping the agent assist the end-user with installation and operation.

1. Resources & Documentation
  • List verified documentation URLs (MUST NOT invent).
  • Link to troubleshooting and community guides.
2. Setup & Installation
  • Document prerequisites and copy-pasteable install commands.
  • Focus heavily on what the user needs to get the software running in their environment.
3. Usage & Running
  • Document primary launch commands and CLI flags.
  • Map key directory structure (ONLY files/dirs users interact with for setup/usage).
- The agent MUST use web search to find actual documentation URLs. - Output length of ~100 lines is STRONGLY RECOMMENDED. - The agent MUST NOT include coding patterns, internal conventions, or development instructions. - The agent MUST use RFC 2119 keywords (MUST, SHOULD, STRONGLY RECOMMENDED). - The agent MUST focus on practical info for assisting users (Setup, Usage, Troubleshooting). - The agent MUST NOT repeat environment metadata or standard tool instructions.

Comments

Markdown supported