Asset and Template Documentation

SKILL.md Preview

---
name: asset-template-documentation
description: Use this skill when the user asks Claude to document, inventory, or write up what is inside a snapshot, template, account export, or asset pack. Trigger when the user mentions describing what a buyer or student gets, documenting a snapshot, or phrases like 'document everything in this so people know what's included.' This skill helps produce a structured asset inventory with setup notes.
compatibility: Claude.ai, Claude Desktop
---

# Asset and Template Documentation

## Purpose
Produce a structured inventory of what a template or snapshot contains, so buyers, students, or teammates know exactly what they are getting and how to use it.

## When to Use This Skill
Use it to document a snapshot, template pack, or asset bundle for sale, delivery, or internal handoff.

## When Not to Use This Skill
Do not use it to build the assets themselves. Do not use it without the actual contents to document.

## Required Inputs
- What the asset is (snapshot, template pack, account export).
- The list or dump of its contents.
- The audience for the documentation (buyer, internal team, student).

## Workflow
1. Confirm the contents are provided; ask for them if only a vague description is given.
2. Write an overview of what the asset is and what it is for.
3. Inventory the contents grouped by type, each item with a one-line purpose.
4. Add setup or install notes and dependencies.
5. Suggest the best way to deploy it.

## Output Format
Return the documentation: Overview, Contents Inventory (grouped by type with purposes), Setup Notes, Dependencies, Suggested Use. Ready to attach to the asset or a sales page.

## Quality Standards
- Inventory is grouped by type and scannable, not a flat list.
- Each item has a plain-language purpose, not just a name.
- Only present contents are documented; ambiguity is flagged.
- Uses contractions, no em dashes, no hype.

## Edge Cases
If the contents dump is incomplete, document what is given and flag gaps rather than assuming. If items are unnamed, describe them by function.

## Safety and Limitations
Document only what is actually present; do not overstate what a bundle includes.

## Test Prompts
1. Here's a list of everything in my GoHighLevel snapshot for med spas. Document it so prospects know exactly what they're buying.
2. Document this template pack for me: it has 12 email templates, 4 funnel pages, and 3 automations. Group it by type with a purpose for each and add install notes.
3. I'm handing a snapshot to a new team member. Write internal documentation explaining what each workflow and form does and what depends on what.

Skill Details

Package Preview

Trigger Phrases

• "Here's a list of everything in my GoHighLevel snapshot for med spas. Document it so prospects know exactly what they're buying."
• "Document this template pack for me: it has 12 email templates, 4 funnel pages, and 3 automations. Group it by type with a purpose for each and add install notes."
• "I'm handing a snapshot to a new team member. Write internal documentation explaining what each workflow and form does and what depends on what."