What is naming-workflows?

A workflow-naming and documentation tool for business processes. It creates short, consistent names and descriptions and records them in an AI Registry, a structured catalogue of workflows.

Use it to name workflows, write workflow descriptions, standardize documentation, and add workflows to an AI Registry.

It removes guesswork and inconsistency from naming workflows. Clear descriptions make workflows easier to find and understand later.

naming-workflows — Skill for Claude Code by jamesgray-ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add jamesgray-ai/handsonai-plugins --skill naming-workflows

Clone the repo

git clone --depth 1 https://github.com/jamesgray-ai/handsonai-plugins

Made for: Claude Code.

Or install handsonai, the plugin that ships this one along with the rest of its 16 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/naming-workflows/github.svg)](https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/naming-workflows)

Your own site

<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/naming-workflows"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/naming-workflows/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/naming-workflows"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/naming-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,364 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.03364
Opus 5.5	$0.00025	$0.01346
Sonnet 5.5	$0.00012	$0.00673
Haiku 4.5	$0.00006	$0.00336

Measured 4d ago against content hash 2be57728a3b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

naming-workflows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/handsonai/skills/naming-workflows/SKILL.md · 264 lines

How it starts

The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Naming Workflows

Generate consistent, professional names and descriptions for business workflows, then record them in the workflow's Workflow node — the workflow's AI Registry entry.

Registry entry: the workflow's registry entry is its Workflow concept node in the registry bundle: registry/ in the working folder: the workspace on Claude Code and Codex; the folder the user selected on Claude desktop; ai-workspace/registry/, or the user's own working folder, in the user's Google Drive or OneDrive on the web and in Microsoft 365, read and written through the platform's connection. See indexing-registry/references/registry-bundle.md (in this plugin) for resolution, write rules, and your fields. If there's no registry/SCHEMA.md, offer the scaffolding-registry skill first; do not write registry entries until the bundle exists.

Workflow Naming Rules

Format Requirements

Length: 2-4 words maximum
Structure: Noun phrases (not verb phrases)
Style: Title Case, each part of a hyphenated word capitalised ("Follow-Up")
Clarity: Self-explanatory without context

Naming Patterns by Domain

Sales workflows:

Pattern: [Prospect Type] [Action]
Examples: Student Enrollment, Lead Qualification, Proposal Generation

Marketing workflows:

Pattern: [Content Type] [Action/Purpose]
Examples: Newsletter Distribution, Social Media Scheduling, Content Repurposing

Product workflows:

Pattern: [Deliverable] [Action]
Examples: Lesson Content Creation, Curriculum Design, Exercise Development

Education workflows:

Pattern: [Student/Cohort] [Activity]
Examples: Student Onboarding, Course Access Setup, Live Session Delivery

Consulting workflows:

Pattern: [Deliverable/Phase] [Action]
Examples: Engagement Planning, Strategic Assessment, Implementation Support

Operations workflows:

Pattern: [Function] [Process]
Examples: Email Response Drafting, Calendar Management, System Maintenance

Finance workflows:

Pattern: [Transaction Type] [Action]
Examples: Invoice Generation, Payment Processing, Revenue Tracking

Read the full file on GitHub · 264 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/examples-by-process.md 8.4 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago Changed · +6 lines 2be57728a3b7
1mo ago Changed · -3 lines dcde67db637c
1mo ago Changed · -1 lines c8bf4f0df36b
1mo ago Changed · +2 lines c7be688dec85
2mo ago First seen · 260 lines · 62 tokens per session scan A 9415eb21f0c9

Subscribe to this mod's changes

naming-workflows is a skill published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 3,364 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Writing and docs

naming-workflows next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
naming-workflowsjamesgray-ai/handsonai-plugins	Skill	8	yesterday	MIT	A	62	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code