How do I install the Artifact Publisher skill?

Run npx skillmds@latest add diegosouzapw/artifact-publisher in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Artifact Publisher safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Artifact Publisher?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Artifact Publisher free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Artifact Publisher?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Artifact Publisher by diegosouzapw — Agent Skill

Name: Artifact Publisher
Rating: 4.2 (5 reviews)
Author: diegosouzapw

File contents

Artifact Publisher Skill

Step 1: Identify Artifact Type

Determine the artifact type and appropriate location:

Type	Location	Format
Plan	`.claude/context/plans/`	`plan-{id}.md`
Report	`.claude/context/reports/`	`report-{type}-{date}.md`
Architecture	`.claude/context/artifacts/`	`architecture-{name}.md`
Schema	`.claude/context/artifacts/`	`schema-{name}.json`
Config	`.claude/context/artifacts/`	`config-{name}.yaml`

Step 2: Add Metadata

Include standard metadata in the artifact:

---
id: artifact-{timestamp}
type: plan|report|architecture|schema|config
title: Artifact Title
created: 2026-01-23T12:00:00Z
author: agent-name
workflow_id: workflow-123
status: draft|final
tags: [tag1, tag2]
---

Step 3: Save Artifact

Write the artifact to the appropriate location:

# Example: Save a plan artifact
Write file_path=".claude/context/plans/plan-auth-2026-01-23.md" content="..."

Step 4: Update References

If the artifact is part of a workflow, update the workflow documentation:

## Artifacts

- Plan: `.claude/context/plans/plan-auth-2026-01-23.md`
- Architecture: `.claude/context/artifacts/architecture-auth.md`

Step 5: Notify Completion

Report the artifact location:

## Artifact Published

**Type**: Plan
**Location**: `.claude/context/plans/plan-auth-2026-01-23.md`
**Status**: Final

Consistent Naming: Use {type}-{name}-{date} format
Include Metadata: Always add creation date and author
Version Important Artifacts: Keep history of major changes
Link Dependencies: Reference related artifacts
Use Appropriate Directory: Follow project conventions

Save this architecture design as a final artifact

Response:

## Artifact Published

**Type**: Architecture
**Title**: User Authentication System
**Location**: `.claude/context/artifacts/architecture-auth-2026-01-23.md`
**Status**: Final

### Metadata

- Created: 2026-01-23T12:00:00Z
- Author: architect
- Tags: authentication, security, jwt

Rules

Always include metadata in artifacts
Use consistent naming conventions
Save to appropriate project directories

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing:

New pattern -> .claude/context/memory/learnings.md
Issue found -> .claude/context/memory/issues.md
Decision made -> .claude/context/memory/decisions.md

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

---name: artifact-publisherdescription: Publish and share artifacts to the project. Use when a user wants to save, share, or finalize generated artifacts.---# Artifact Publisher Skill<identity>Artifact Publisher - Handles the lifecycle of artifacts, ensuring they are properly versioned, saved, and documented.</identity><capabilities>- Saving artifacts to project directories- Versioning artifact files- Adding metadata to artifacts- Linking related artifacts</capabilities><instructions><execution_process>### Step 1: Identify Artifact TypeDetermine the artifact type and appropriate location:| Type | Location | Format || ------------ | ---------------------------- | ------------------------- || Plan | `.claude/context/plans/` | `plan-{id}.md` || Report | `.claude/context/reports/` | `report-{type}-{date}.md` || Architecture | `.claude/context/artifacts/` | `architecture-{name}.md` || Schema | `.claude/context/artifacts/` | `schema-{name}.json` || Config | `.claude/context/artifacts/` | `config-{name}.yaml` |### Step 2: Add MetadataInclude standard metadata in the artifact:```markdown---id: artifact-{timestamp}type: plan|report|architecture|schema|configtitle: Artifact Titlecreated: 2026-01-23T12:00:00Zauthor: agent-nameworkflow_id: workflow-123status: draft|finaltags: [tag1, tag2]---```### Step 3: Save ArtifactWrite the artifact to the appropriate location:```bash# Example: Save a plan artifactWrite file_path=".claude/context/plans/plan-auth-2026-01-23.md" content="..."```### Step 4: Update ReferencesIf the artifact is part of a workflow, update the workflow documentation:```markdown## Artifacts- Plan: `.claude/context/plans/plan-auth-2026-01-23.md`- Architecture: `.claude/context/artifacts/architecture-auth.md````### Step 5: Notify CompletionReport the artifact location:```markdown## Artifact Published**Type**: Plan**Location**: `.claude/context/plans/plan-auth-2026-01-23.md`**Status**: Final```</execution_process><best_practices>1. **Consistent Naming**: Use `{type}-{name}-{date}` format2. **Include Metadata**: Always add creation date and author3. **Version Important Artifacts**: Keep history of major changes4. **Link Dependencies**: Reference related artifacts5. **Use Appropriate Directory**: Follow project conventions</best_practices></instructions><examples><usage_example>**Publish Request**:```Save this architecture design as a final artifact```**Response**:```markdown## Artifact Published**Type**: Architecture**Title**: User Authentication System**Location**: `.claude/context/artifacts/architecture-auth-2026-01-23.md`**Status**: Final### Metadata- Created: 2026-01-23T12:00:00Z- Author: architect- Tags: authentication, security, jwt```</usage_example></examples>## Rules- Always include metadata in artifacts- Use consistent naming conventions- Save to appropriate project directories## Memory Protocol (MANDATORY)**Before starting:**```bashcat .claude/context/memory/learnings.md```**After completing:**- New pattern -> `.claude/context/memory/learnings.md`- Issue found -> `.claude/context/memory/issues.md`- Decision made -> `.claude/context/memory/decisions.md`> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Frequently asked questions

Artifact Publisher