When should a prompt become a Skill?

Compare the maintenance burden

Look for a repeated procedure

Suppose each weekly update needs the same evidence check, narrative order and output validation. If you repeatedly paste those steps, maintain several variants or carry example files between chats, a Skill may be easier to review and update.

If the task is simply to rewrite one paragraph with a new tone, a clear prompt may be enough. Packaging a vague instruction does not make it more reliable.

Separate the method from the task data

Read the approved inputs.
Identify unsupported claims.
Organize progress, risk and decisions.
Create the documented output format.
Check the files against the brief.

Reporting period: this week
Audience: internal product team
Inputs: brief.md and metrics.csv
Decision needed: choose the next milestone

Keep facts, client names and time-sensitive numbers out of a generic method unless they truly belong to the package's purpose. Use examples with clear labels so they are not mistaken for real inputs.

Test the package before relying on reuse

• A normal request with complete inputs.
• A request with one missing source.
• A task outside the intended scope.
• A revision that must preserve approved facts.

Inspect the actual output files for all four cases. The benefit of a reusable method should be visible in consistency, clearer boundaries or less repeated setup, not merely in having a folder.

FAQ