원클릭으로 Manus에서 모든 스킬 실행

시작하기

document

스타6

포크0

업데이트2026년 6월 1일 17:36

Generates standardized documentation (troubleshooting, guides, architecture) with consistent frontmatter.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

SamPlaysKeys

SamPlaysKeys/Workspace

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Document

Create consistent, frontmatter-rich documentation. This skill is often called at the end of a `troubleshoot` or `storm session` to graduate findings into permanent reference material.

Triggers

User asks to "write this up", "document this", or "create a guide".
Handoff from the troubleshoot skill.

Process

Determine the type of document requested (Troubleshooting vs. Guide).
Extract the relevant context from the conversation history, especially the primary external reference URL.
Generate the document using the exact templates below.
Save to the appropriate directory (docs/troubleshooting/ or docs/guides/).

Templates

1. Troubleshooting (Remediation)

Use when: Documenting a specific error, bug, or failure and how to fix it. Path: docs/troubleshooting/<system>/<issue-name>.md

---
type: Troubleshooting
status: Active
system: [System Name]
related_to: []
references: []
---

# Fixing [Issue Name] on [System]

## Symptoms
[What the user sees, exact error messages, stack traces]

## Root Cause
[Brief explanation of why it failed]

## Resolution
[Step-by-step fix]
1. ...
2. ...

## Verification
[How to confirm it's fixed]

## References
[Less is more. If a single authoritative resource covers the solution, only include that one.]
- [Link Title](URL) - [Brief note on what this link provided]

2. Guide (Prevention / Setup)

Use when: Documenting how to set something up correctly, or how to avoid an issue entirely. Path: docs/guides/<system>/<topic>.md

---
type: Guide
status: Active
system: [System Name]
related_to: []
references: []
---

# [Topic / Setup] for [System]

## Overview
[What this configures and why it matters]

## Prerequisites
- [Requirement 1]

## Configuration
[Step-by-step setup]
1. ...
2. ...

## Common Pitfalls
[What to avoid, learned from past troubleshooting]

## References
[Less is more. If a single authoritative resource covers the solution, only include that one.]
- [Link Title](URL) - [Brief note on what this link provided]

이 저장소의 다른 Skills

같은 저장소

handoff

SamPlaysKeys/Workspace

Captures session state for future continuation. Auto-triggers when the user says "drop a breadcrumb", "dead drop", "close out", or asks to pause/wrap up.

2026-06-036

start

SamPlaysKeys/Workspace

Quick session orientation — surfaces state, recent handoffs, and suggests focus. Auto-triggers on "where were we", "what's next", or explicitly starting a session.

2026-06-036

consolidate

SamPlaysKeys/Workspace

Organizes a messy WIP/Storm Session folder into a structured Abstract and Table of Contents. Auto-triggers on "consolidate this", "organize the wip", or "create a brief".

2026-06-016

cross-link

SamPlaysKeys/Workspace

Finds and fixes missing index links for newly created files to prevent orphans. Auto-triggers when completing documentation.

2026-06-016

ideate

SamPlaysKeys/Workspace

Quarantined workspace for brainstorming and rapid ideation. Auto-triggers when the user says "storm session", "storm sesh", "brainstorm", or "let's ideate".

2026-06-016

troubleshoot

SamPlaysKeys/Workspace

Structured debugging and problem solving. Auto-triggers when the user reports an error, bug, or unexpected behavior. Supports fast (default) and slow modes.

2026-06-016

Document

Triggers

User asks to "write this up", "document this", or "create a guide".

Handoff from the troubleshoot skill.

Process

Determine the type of document requested (Troubleshooting vs. Guide).

Extract the relevant context from the conversation history, especially the primary external reference URL.

Generate the document using the exact templates below.

Save to the appropriate directory (docs/troubleshooting/ or docs/guides/).

Templates

1. Troubleshooting (Remediation)

Use when: Documenting a specific error, bug, or failure and how to fix it. Path: docs/troubleshooting/<system>/<issue-name>.md

--- type: Troubleshooting status: Active system: [System Name] related_to: [] references: [] --- # Fixing [Issue Name] on [System] ## Symptoms [What the user sees, exact error messages, stack traces] ## Root Cause [Brief explanation of why it failed] ## Resolution [Step-by-step fix] 1. ... 2. ... ## Verification [How to confirm it's fixed] ## References [Less is more. If a single authoritative resource covers the solution, only include that one.] - [Link Title](URL) - [Brief note on what this link provided]

2. Guide (Prevention / Setup)

Use when: Documenting how to set something up correctly, or how to avoid an issue entirely. Path: docs/guides/<system>/<topic>.md

--- type: Guide status: Active system: [System Name] related_to: [] references: [] --- # [Topic / Setup] for [System] ## Overview [What this configures and why it matters] ## Prerequisites - [Requirement 1] ## Configuration [Step-by-step setup] 1. ... 2. ... ## Common Pitfalls [What to avoid, learned from past troubleshooting] ## References [Less is more. If a single authoritative resource covers the solution, only include that one.] - [Link Title](URL) - [Brief note on what this link provided]

name	document
description	Generates standardized documentation (troubleshooting, guides, architecture) with consistent frontmatter.