# Installation and manual use

The same instructions can be used as plain text, an uploaded playbook, project knowledge, or discoverable skills. Choose the route actually supported by the user's AI application.

## Inspect before choosing a destination

Determine whether this session can read files, write files, access persistent knowledge, discover skills, browse current documentation, or install integrations. Confirm whether it is running locally or in a hosted environment.

Inspect supported skill roots through the host's configuration or current official guidance. Do not assume that a folder name works across products. Ask for the preferred project or personal scope if it is still unresolved.

If the host has no discoverable skills mechanism, use the combined playbook as an attachment or pasted instructions. Do not make skill installation a barrier to starting useful planning.

## Prepare the installation plan

Locate the source package and list its eight folders:
- small-business-marketing-intake
- product-marketing
- content-strategy
- copywriting
- social
- ad-creative
- video
- analytics

For a compatible host, each folder must retain its SKILL.md and local references. Copy complete folders to the verified root. Do not flatten identically named entrypoints into one directory.

Show the exact target, scope, affected files, conflicts, and selected tool setup steps before requesting any missing authorization. If that plan is already authorized, proceed within its limits.

If only the combined playbook is available, reconstruct eight self-contained SKILL.md files from its eight workflow sections. Include each workflow's referenced guide sections inline, add the listed skill name and a concise description as frontmatter, and change section links to matching local headings. Check that no required guidance was omitted. Label these as reconstructed copies, rather than claiming a byte-identical folder installation. Prepare them as downloadable Markdown when direct writing is unavailable.

## Preserve existing work

Compare existing files first. Leave identical files in place. Copy missing folders when permitted. When a same-named skill differs, preserve it and resolve whether to keep it or perform an explicitly authorized backed-up update.

For an approved replacement, keep the backup outside active skill discovery, record its location, and change only the selected skill. Check resolved paths before moving or replacing folders. Reject unexpected path traversal or symlink redirection.

Do not remove unrelated configuration or replace the host's instruction files without a specific reason and authorization. An optional compatibility pointer may be merged into an existing instruction file only when that edit is within scope.

## Verify the result

Check each entrypoint, name, supporting reference, and copied byte content. Then confirm discovery through the host's actual skill list, selector, or a documented equivalent. If refresh or a new session is needed, record that state.

A copied file is not yet a verified discovered skill. A skill is not an installed tool, and an installed connector is not authenticated account access.

If the host accepts individual skill uploads, follow its current archive layout and upload process. If it only accepts documents, provide the combined playbook or the requested individual workflow.

## Configure tools after the brief

Choose tools by the agreed capabilities and budget. Use existing first-party connectors or official installation sources. Verify the publisher and the host-supported route rather than inventing identifiers or commands.

Automatically perform authorized installation and configuration where available. Use the host's real permission mechanism when needed. Guide the owner through authentication or administrator actions that require them.

Do not buy a plan, spend credits, publish a post, send outreach, or change a live campaign merely to prove connectivity unless that action is separately within the user's authority. Start verification with an appropriate low-impact read operation.

Record success, limitations, and next steps. After a failure, inspect the cause and change the relevant condition before retrying; avoid repeated billable attempts. Continue independent setup while an owner step is pending.