| name | potato:create-artifacts |
| description | You MUST use this skill in order to create, update, edit, or build artifacts or files. Artifacts can be of any type but are typically markdown files. |
Overview
This skill provides guidence on how to properly write and save an artifact.
To create an artifact perform the following steps:
- Write the artifact and save it.
- Attach the artifact to the ticket.
Writing Artifacts
Artifacts are saved to .potato/cache/tickets/{ticketId}/artifacts/ where {ticketId} is the current ticket/ticket identifier.
Example:
.potato/cache/tickets/POT-2/artifacts/refinement.md
.potato/cache/tickets/POT-2/artifacts/architecture.md
.potato/cache/tickets/POT-2/artifacts/diagram.pdf
- Determine the current
ticketId from context
- Write the artifact to the appropriate file
Attaching the Artifact
Artifact files can and should be attached to tickets, to attach an artifact to a ticket you must using the attach_artifact MCP tool:
attach_artifact(
file_path: ".potato/cache/tickets/{ticketId}/artifacts/{artifact-name}.{ext}",
artifact_type: ".md" | ".txt" | ".pdf" | etc.,
description: "Optional description of the artifact"
)
Example:
attach_artifact(
file_path: ".potato/cache/tickets/POT-2/artifacts/refinement.md",
artifact_type: ".md",
description: "Initial requirements refinement"
)
Guidelines
- Always use the ticketId - Never save artifacts without a ticket context
- Overwrite/update allowed - Artifacts can be updated/overwritten as needed
