Agent skill

Artifact Naming

Naming conventions for artifact kind and path, ensuring data can be aggregated and analyzed

Apache-2.0Auto-check passedMarketing & SEO

Install Artifact Naming

skills CLI

$ npx skills add chekusu/wanman --skill artifact-naming -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install chekusu/wanman artifact-naming --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/chekusu/wanman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/artifact-naming .claude/skills/artifact-naming && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "artifact-naming" agent skill from https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming into .claude/skills/artifact-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-naming", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add chekusu/wanman --skill artifact-naming -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install chekusu/wanman artifact-naming --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/chekusu/wanman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/skills/artifact-naming .agents/skills/artifact-naming && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "artifact-naming" agent skill from https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming into .agents/skills/artifact-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-naming", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add chekusu/wanman --skill artifact-naming -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install chekusu/wanman artifact-naming --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/chekusu/wanman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/skills/artifact-naming .cursor/skills/artifact-naming && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "artifact-naming" agent skill from https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming into .cursor/skills/artifact-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-naming", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/chekusu/wanman.git --path packages/core/skills/artifact-naming

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add chekusu/wanman --skill artifact-naming -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install chekusu/wanman artifact-naming --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/chekusu/wanman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/skills/artifact-naming .gemini/skills/artifact-naming && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "artifact-naming" agent skill from https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming into .gemini/skills/artifact-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-naming", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install chekusu/wanman artifact-naming

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add chekusu/wanman --skill artifact-naming -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/chekusu/wanman.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/skills/artifact-naming .github/skills/artifact-naming && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "artifact-naming" agent skill from https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming into .github/skills/artifact-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-naming", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add chekusu/wanman --skill artifact-naming -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install chekusu/wanman artifact-naming --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/chekusu/wanman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/skills/artifact-naming .opencode/skills/artifact-naming && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "artifact-naming" agent skill from https://github.com/chekusu/wanman/tree/main/packages/core/skills/artifact-naming into .opencode/skills/artifact-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-naming", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: artifact-naming
GitHub stars: 688
Token cost: ~1.1k tokens
SKILL.md length: 178 words
Files: 1
Skills in repo: 6
Repo updated: Jun 14, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Naming conventions for artifact kind and path, ensuring data can be aggregated and analyzed

Marketing & SEO work in your project
SKILL.md covers Important: --path Is a…, Important: Use --file to Store…, Kind Standardization and Path Naming Convention…, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Artifact Naming is an agent skill from chekusu/wanman. Naming conventions for artifact kind and path, ensuring data can be aggregated and analyzed

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO. The repository describes itself as: wanman is an open-source agent matrix runtime inspired by Japanese one-man trains. It lets human users step back into an observer role while local agent runtimes coordinate… The licence is Apache-2.0.

When your agent uses it

Marketing & SEO work in your project

Example prompts

“/artifact-naming”

What it can do on your machine

Read from SKILL.md and the folder at commit d3a8138. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Artifact Naming loads about 1.1k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 178 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~27
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from chekusu/wanman at commit d3a8138, republished under its Apache-2.0 licence (© chekusu). 178 words, ~1,069 tokens.

Download SKILL.mdSave it as .claude/skills/artifact-naming/SKILL.md (or your agent's skills folder).

name: artifact-naming
description: Naming conventions for artifact kind and path, ensuring data can be aggregated and analyzed

Artifact Naming Conventions

Important: --path Is a Required Parameter

Every call to wanman artifact put must include the --path parameter. Artifacts without a path cannot be retrieved or aggregated.

bash

# Full command format
wanman artifact put --kind <kind> --path "<domain>/<category>/<item>" --source "<source>" --confidence <0-1> '<json>'

Important: Use --file to Store Output File Contents

After writing an MD/HTML or other file, use the --file parameter to store the file contents in the artifact. This ensures file contents are version-controlled in the database.

bash

# After writing a file, include --file in artifact put
wanman artifact put --kind brand_asset --path "brand/identity/handbook" \
  --source "marketing" --confidence 0.9 \
  --file /workspace/agents/output/marketing/brand-design.md \
  '{"name":"Brand Handbook","type":"handbook"}'

# Structured data (no file) does not need --file
wanman artifact put --kind budget_item --path "costs/opex/rent" \
  --source "estimate" --confidence 0.4 \
  '{"item":"rent","amount":350000,"currency":"JPY"}'

Rule: If your task output includes MD or HTML files, you must include --file pointing to that file when calling artifact put.

Kind Standardization

Only use the following standard kind values — do not invent your own:

Domain	Standard Kind	Description
Market research	`competitor`	Competitor information
Market research	`market_data`	Market data (size, trends)
Market research	`customer_profile`	Customer personas
Market research	`location_data`	Location-related data
Finance	`budget_item`	Individual cost item (use this uniformly, not monthly_cost/initial_investment)
Finance	`revenue_forecast`	Revenue forecast
Finance	`financial_summary`	Financial summary (break-even, payback period, etc.)
Branding	`brand_asset`	Brand asset (name, story, visuals, tagline — all under brand_asset)
Content	`content_plan`	Content planning
Technical	`tech_spec`	Technical specification

Path Naming Convention (Required)

Format: {domain}/{category}/{item}

costs/capex/renovation        ← One-time renovation cost
costs/capex/equipment          ← Equipment procurement
costs/opex/rent               ← Monthly rent
costs/opex/labor              ← Monthly labor
costs/opex/materials          ← Raw material costs
market/competitors/cafe-a     ← Competitor A
market/competitors/cafe-b     ← Competitor B
market/demographics/target    ← Target customer segment
market/location/rent-level    ← Rent level
brand/naming/candidate-1      ← Brand name candidate 1
brand/naming/candidate-2      ← Brand name candidate 2
brand/visual/colors           ← Color system
brand/visual/typography       ← Typography direction
brand/story/core              ← Brand story
brand/slogan/main             ← Brand tagline
content/social/instagram      ← Instagram plan
content/social/twitter        ← Twitter plan
revenue/forecast/monthly      ← Monthly revenue forecast
revenue/forecast/breakeven    ← Break-even analysis
finance/summary/cashflow      ← Cash flow summary
tech/website/spec             ← Website technical specification

Correct vs. Incorrect Examples

bash

# Wrong: kind is too granular, no path
wanman artifact put --kind initial_investment --source "estimate" --confidence 0.4 '{"item":"equipment"}'
wanman artifact put --kind monthly_cost --source "estimate" --confidence 0.4 '{"item":"rent"}'
wanman artifact put --kind brand_name_candidate --source "original" --confidence 0.8 '{"name":"ITTEKI"}'

# Correct: standard kind + path for differentiation
wanman artifact put --kind budget_item --path "costs/capex/equipment" --source "estimate" --confidence 0.4 '{"item":"equipment","amount":500000}'
wanman artifact put --kind budget_item --path "costs/opex/rent" --source "estimate" --confidence 0.4 '{"item":"rent","amount":350000}'
wanman artifact put --kind brand_asset --path "brand/naming/candidate-1" --source "original" --confidence 0.8 '{"name":"ITTEKI","meaning":"one drop"}'

Files

Just SKILL.md in packages/core/skills/artifact-naming of chekusu/wanman.

Open the folder on GitHubat commit d3a8138

Compare with similar skills

Artifact Naming next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Artifact Naming compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Artifact Naming this skillchekusu/wanman	688	—	~1.1k	Automated safety check: Pass	Apache-2.0	3 mo ago
Geo Fundamentalswasp-lang/wasp	19k	9 repos	~861	Automated safety check: Pass	MIT	yesterday
Ab Testingcoreyhaines31/marketingskills	54k	3 repos	~3.1k	Automated safety check: Pass	MIT	yesterday
Hreflang and International SEOAgriciDaniel/claude-seo	19k	5 repos	~3.4k	Automated safety check: Pass	MIT	5 days ago
Referralscoreyhaines31/marketingskills	54k	2 repos	~2.6k	Automated safety check: Pass	MIT	yesterday
SEO GeoReScienceLab/opc-skills	1.8k	4 repos	~2.1k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
19k GitHub starsUsed in 9 repos~861 tokens
Marketing & SEOAuto-check passed
Ab Testing
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
54k GitHub starsUsed in 3 repos~3.1k tokens
Marketing & SEOAuto-check passed
Hreflang and International SEO
AgriciDaniel/claude-seo
Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.
19k GitHub starsUsed in 5 repos~3.4k tokens
Marketing & SEOAuto-check passed
Referrals
coreyhaines31/marketingskills
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.
54k GitHub starsUsed in 2 repos~2.6k tokens
Marketing & SEOAuto-check passed
SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
1.8k GitHub starsUsed in 4 repos~2.1k tokens
Marketing & SEOAuto-check passed
Ad Creative
LeoYeAI/openclaw-marketing-skills
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
1k GitHub starsUsed in 8 repos~3.4k tokens
Marketing & SEOAuto-check passed

Questions about Artifact Naming

What does Artifact Naming do?

Naming conventions for artifact kind and path, ensuring data can be aggregated and analyzed. Artifact Naming is an agent skill from chekusu/wanman.

When should I use Artifact Naming?

Artifact Naming fits situations like: marketing & SEO work in your project.

How do I install Artifact Naming in Claude Code?

Run `npx skills add chekusu/wanman --skill artifact-naming -a claude-code`. Or copy the skill folder (packages/core/skills/artifact-naming in chekusu/wanman) into .claude/skills/artifact-naming in your project. Claude Code loads it when a task matches its description.

How do I install Artifact Naming in Codex?

Run `npx skills add chekusu/wanman --skill artifact-naming -a codex`. Or copy the skill folder (packages/core/skills/artifact-naming in chekusu/wanman) into .agents/skills/artifact-naming in your project. Codex loads it when a task matches its description.

Can I use Artifact Naming in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add chekusu/wanman --skill artifact-naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/artifact-naming, .gemini/skills/artifact-naming, .github/skills/artifact-naming and .opencode/skills/artifact-naming in your project.

What does Artifact Naming need to run?

SKILL.md names no scripts, command-line tools or credentials: Artifact Naming is instructions for the agent only.

Does Artifact Naming access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Artifact Naming safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Artifact Naming use?

Artifact Naming is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Artifact Naming use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Artifact Naming?

Skills that share tags, products or a category with Artifact Naming: Geo Fundamentals (wasp-lang/wasp, 19k stars), Ab Testing (coreyhaines31/marketingskills, 54k stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 19k stars) and Referrals (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Artifact Naming?

chekusu (a GitHub organization) maintains it in chekusu/wanman, which has 688 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 14, 2026.

Source: chekusu/wanman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Artifact Naming

Install Artifact Naming

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Artifact Naming Conventions

Important: --path Is a Required Parameter

Important: Use --file to Store Output File Contents

Kind Standardization

Path Naming Convention (Required)

Correct vs. Incorrect Examples

Files

Compare with similar skills

Similar skills

Geo Fundamentals

Ab Testing

Hreflang and International SEO

Referrals

SEO Geo

Ad Creative

More from chekusu/wanman

Artifact Quality

Cross Validation

Research Methodology

Wanman CLI

Workspace Conventions

Questions about Artifact Naming

Install Artifact Naming

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Artifact Naming Conventions

Important: --path Is a Required Parameter

Important: Use --file to Store Output File Contents

Kind Standardization

Path Naming Convention (Required)

Correct vs. Incorrect Examples

Files

Compare with similar skills

Similar skills

More from chekusu/wanman

Related

Questions about Artifact Naming