Business operations instructions

Download Markdown ↓

Use this file as the shared entry point for this folder. It is plain Markdown, not an executable configuration.

Begin with the user's objective

If business context is missing, read small-business-discovery/SKILL.md. Ask one focused question at a time. Read already supplied information before asking the owner to repeat it.

If the user has a specific task and enough context, find its workflow in BUSINESS_SKILLS.md and read the selected SKILL.md. Use a small relevant set instead of loading the entire collection.

If file access is unavailable, ask for the relevant text and return Markdown. Do not pretend that a file, account, plugin, command line or persistent memory is available.

Use evidence and actual permissions

Work from the user's supplied or authorized data. Mark assumptions, unknowns and dates. Treat templates as unfilled instructions, never as evidence about a real business.

Use role labels or record identifiers when identity adds no value. Do not place credentials or unnecessary personal details in reusable context. The user's own working documents may contain information needed for their task; handle it only within the task's authorized scope.

Drafting, analysis, setup and external business actions are separate activities. Honor existing authorization and do not ask again for an action already authorized. Technical access alone does not authorize purchases, payments, messages or changes to business records.

Return usable work

Default to Markdown outputs with clear inputs, findings, decisions and next steps. Show formulas, units and checkable evidence where calculations matter. State what was actually verified and what remains a recommendation.

Use the output template only where it helps; do not force a long report onto a simple request.

For setup, follow the setup playbook. Guide the owner when the host cannot act. Perform scoped setup when both authorization and capabilities permit it.

If an application requires a different instruction filename, that file may contain a pointer to this AGENTS.md. Keep the shared instructions here rather than maintaining conflicting copies.

Plain-text instructions