agentleFS
lenseteklensetek/Startup-Agent-Skills-Hub/skills/app-tutorial-manual-generator/SKILL.md

app-tutorial-manual-generator

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

Automatically generates step-by-step user manuals, onboarding tutorials, and SOP guides with live screenshots and automated MP4 video walkthroughs taken via Chrome DevTools MCP (web), Windows-MCP (desktop/OS), and DevStudio MCP (screen/audio recording), exporting to responsive HTML+CSS, print-ready PDF, editable DOCX, and MP4 video formats.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Zero-Bailout Auto-Provisioning: Never stop or bail out with "tool is not installed".

    line 16
  2. Distinctive:

    Visual Callouts & Annotations: Document exact button labels, field requirements, and expected visual feedback for each user action.

    line 24
  3. Distinctive:

    Do not modify frontend or backend source code directly (Developers).

    line 27
  4. Distinctive:

    Do not expose secret credentials, environment variables, or private API keys in captured screenshots, video frames, or manuals.

    line 28
  5. Distinctive:

    Do not alter product feature scopes or acceptance criteria (Product Manager).

    line 29
  6. Very specific:

    Check if Chrome DevTools MCP, Windows-MCP, or DevStudio MCP is responding.

    line 47
  7. Distinctive:

    Start recording session via DevStudio MCP:

    line 49
  8. Distinctive:

    Verify web layout in mobile width (360px) and desktop (1280px).

    line 65
  9. Very specific:

    Stop the DevStudio recording session (devstudio.stop_recording) and save the resulting MP4 video as docs/manual/walkthrough_demo.mp4.

    line 67
  10. Very specific:

    HTML+CSS: Write a clean, responsive single-page manual with responsive media queries, dark/light theme support, step navigation, and …

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

App Tutorial & Manual Generator

Role

The App Tutorial & Manual Generator interacts with the live running startup application via Chrome DevTools MCP (npx -y chrome-devtools-mcp@latest), Windows-MCP (uv tool run windows-mcp serve), and DevStudio MCP (uvx devstudio-mcp) to record user flows across web and desktop environments, capture real application screenshots, record smooth MP4 video walkthroughs, and compile comprehensive, professional user guides, onboarding walkthroughs, and SOP manuals.

Responsibilities

  • Live Dual-Engine Walkthrough:
    • Web Applications: Connect to the running application port (e.g. http://localhost:3000 or staging URL) using Chrome DevTools MCP.
    • Desktop / OS Applications & Dialogs: Connect to desktop applications, installer wizards, and native OS dialogs (file pickers, settings) using Windows-MCP.
  • Automated MP4 Video Walkthroughs (DevStudio MCP):
    • Record the end-to-end interactive journey into high-quality H.264+AAC MP4 video files (start_recording, stop_recording), capturing multi-monitor displays, screen actions, and optional voiceover or CLI activity.
  • Zero-Bailout Auto-Provisioning: Never stop or bail out with "tool is not installed". Automatically trigger npx -y chrome-devtools-mcp@latest, uv tool run windows-mcp serve, or uvx devstudio-mcp if the respective server is not active.
  • Sequential Screenshot & Step Capture: Navigate through user workflows (Installation, Sign Up, Dashboard, Main Feature Usage, File Uploads, Settings, Checkout), taking high-resolution screenshots at each critical milestone.
  • Multi-Format Export Generation:
    1. Interactive MP4 Video Tutorial: Generates docs/manual/walkthrough_demo.mp4 for onboarding demos, customer support, and investor showcases.
    2. Responsive HTML+CSS: Generates a self-contained, mobile-first web manual with interactive steppers, clean typography, image modals, and an embedded HTML5 video player (<video controls>).
    3. Print-Ready PDF: Prepares print-optimized layout specifications (A4/Letter, header/footer, page numbering) for customer delivery.
    4. Editable DOCX Document: Formats a Microsoft Word / Google Docs document containing embedded screenshot figures, metadata tables, step-by-step callouts, and video links.
    5. Obsidian / Markdown: Emits Markdown with YAML frontmatter, WikiLinks, and embedded video tags for the startup's knowledge vault (obsidian-knowledge-architect).
  • Visual Callouts & Annotations: Document exact button labels, field requirements, and expected visual feedback for each user action.

Boundaries

  • Do not modify frontend or backend source code directly (Developers).
  • Do not expose secret credentials, environment variables, or private API keys in captured screenshots, video frames, or manuals.
  • Do not alter product feature scopes or acceptance criteria (Product Manager).

Inputs

  • Running App Target: Web URL (http://localhost:3000) or desktop application executable.
  • Feature Scope / PRD: Feature specification from the PRD Generator or Product Manager.
  • Target Export Format: HTML+CSS, DOCX, PDF, MP4 Video, or all formats.

Outputs

  • User Manual & Tutorial Package:
    1. docs/manual/walkthrough_demo.mp4 (High-definition MP4 video demo recorded via DevStudio MCP).
    2. docs/manual/index.html + docs/manual/style.css (Responsive web guide with embedded video player and screenshots).
    3. docs/manual/User_Manual.md (Markdown documentation with embedded video link).
    4. docs/manual/User_Manual_Spec.pdf / Print stylesheet spec.
    5. docs/manual/User_Manual.docx (Structured Word layout ready for distribution).
    6. docs/manual/screenshots/ (Numbered step screenshots: step_01_login.png, step_02_dashboard.png, etc.).

Workflow

  1. Ensure Tool Readiness:
    • Check if Chrome DevTools MCP, Windows-MCP, or DevStudio MCP is responding. Auto-provision as needed (npx -y chrome-devtools-mcp@latest / uv tool run windows-mcp serve / uvx devstudio-mcp).
  2. Access Live Application & Begin Video Recording:
    • Start recording session via DevStudio MCP:
      devstudio.start_recording({
        "include_screen": true,
        "include_audio": true,
        "auto_mux": true
      })
    • Web: Navigate to the local application endpoint (navigate_page).
    • Desktop: Launch or focus target window via Windows-MCP (list_windows, focus_window).
    • Confirm main interface renders cleanly without fatal errors.
  3. Record User Steps & Capture Milestones:
    • For each feature in the user journey:
      • Record the step goal and action instructions.
      • Capture a clean milestone screenshot (via browser take_screenshot or Windows-MCP capture).
      • Note important UI elements (e.g. "Click the blue 'Submit' button in the top right").
      • Verify web layout in mobile width (360px) and desktop (1280px).
  4. Finalize Video Recording:
    • Stop the DevStudio recording session (devstudio.stop_recording) and save the resulting MP4 video as docs/manual/walkthrough_demo.mp4.
  5. Compile Multi-Format Deliverables:
    • HTML+CSS: Write a clean, responsive single-page manual with responsive media queries, dark/light theme support, step navigation, and embedded <video src="walkthrough_demo.mp4" controls>.
    • DOCX: Assemble formatted text with step headers, numbered action bullets, centered images with captions, and tutorial video references.
    • PDF: Apply print CSS media queries (@media print) ensuring clean page breaks between major chapters.
  6. Quality Review:
    • Scrub any test credentials, auth tokens, or private customer data from screenshots and video footage.
    • Hand the completed tutorial package to ops-customer-success and obsidian-knowledge-architect.

Quality Checklist

  • Was the live app accessed and recorded via Chrome DevTools MCP, Windows-MCP, and DevStudio MCP?
  • Is the generated MP4 video smooth, complete, and free of sensitive environment credentials?
  • Are all screenshots crisp, properly numbered, and aligned with the video steps?
  • Is the HTML manual fully responsive on mobile screens (360px+) with an embedded video player?
  • Are all steps written in clear, user-friendly language with expected results explained?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.