naming-workflows

naming-workflows is a skill for Claude Code from jamesgray-ai/handsonai-plugins. It costs 62 tokens per session (2,920 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it to name workflows, write workflow descriptions, standardize documentation, and add workflows to an AI Registry.
Why use it?
It removes guesswork and inconsistency from naming workflows. Clear descriptions make workflows easier to find and understand later.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the handsonai plugin — 13 skills, 1 agent shipped together

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.

agentmods
npx agentmods add skills/jamesgray-ai/handsonai-plugins/naming-workflows
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 13 skills, 1 agent.

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.

agentmods badge for naming-workflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/naming-workflows.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.svg" alt="Measured on agentmods" 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 2,920 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.02920
Opus 5 $0.00031 $0.01460
Sonnet 5 $0.00012 $0.00584
Haiku 4.5 $0.00006 $0.00292

Measured 5d ago against content hash 9415eb21f0c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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 · 260 lines

How it starts

The opening of the file, as written. The whole thing — 260 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 workspace's registry/ bundle — see indexing-registry/references/registry-bundle.md (in this plugin) for resolution, write rules, and your fields. If the workspace has no registry/SCHEMA.md, offer the scaffolding-registry skill first (it also migrates legacy workflow.yaml workspaces); 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
  • 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

Common Patterns

| If workflow monitors/checks | Use "[Subject] Monitoring" or "[Subject] Review" | | If workflow creates output | Use "[Output] Creation" or "[Output] Generation" | | If workflow sends/distributes | Use "[Item] Distribution" or "[Item] Delivery" | | If workflow onboards/sets up | Use "[Subject] Onboarding" or "[Subject] Setup" | | If workflow recovers/follows up | Use "[Subject] Recovery" or "[Subject] Follow-up" |

Read the full file on GitHub · 260 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.

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.

  1. 5d 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 24d ago), licensed MIT. It adds 62 tokens to every session and 2,920 once invoked, about $0.0003 per session on Opus 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens