Agent skill

Creating Process Files

by lexler in lexler/skill-factory

Creates process files - text as code instructions for reliable AI workflows.

Apache-2.0Auto-check passed

Install Creating Process Files

skills CLI
$ npx skills add lexler/skill-factory --skill creating-process-files -a claude-code

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

GitHub CLI
$ gh skill install lexler/skill-factory creating-process-files --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/lexler/skill-factory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/output_skills/ai/creating-process-files .claude/skills/creating-process-files && 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/

Facts

Skill name
creating-process-files
GitHub stars
239
Token cost
~566 tokens
SKILL.md length
329 words
Files
2
Skills in repo
25
Repo updated
First seen
Licence
Apache-2.0

At a glance

Creates process files - text as code instructions for reliable AI workflows.

  • Works in 4 steps: Interview → Draft → Clarification → …
  • Creating new process files
  • SKILL.md covers Description, Steps, Pieces and Interview Protocol, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Creating Process Files is an agent skill from lexler/skill-factory. Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `credits.md`).

The licence is Apache-2.0.

When your agent uses it

  • Creating new process files

Example prompts

  • “Use the creating-process-files skill to create process files - text as code instructions for reliable AI workflows”
  • “/creating-process-files”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Interview
  2. Draft
  3. Clarification
  4. Simplification

What it can do on your machine

Read from SKILL.md and the folder at commit 8017333. 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.

    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

Creating Process Files loads about 566 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 329 words of instructions outside code blocks.

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

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 lexler/skill-factory at commit 8017333, republished under its Apache-2.0 licence (© lexler). 329 words, ~566 tokens.

Download SKILL.mdSave it as .claude/skills/creating-process-files/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
creating-process-files
description
Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files.

Creating Process Files

STARTER_CHARACTER = ⚙️

Description

This skill helps make new process files or fine tune existing ones. A process file describes a structured sequence of steps for AI to follow to create a predictable output. Process files are content neutral to the project.

Steps

This process has these distinct phases:

  1. Interview Phase - Ask for the pieces of the process file that we are going to build
  2. Draft Phase - Create the initial version of the process file
  3. Clarification Phase - Ask any clarifying questions about the process file
  4. Simplification Phase - Remove unnecessary content

Pieces

  • [FILE_NAME]
  • [HEADER]
  • [STARTER_CHARACTER]
  • Steps
    • Title
    • Details
    • Sub-steps (optional)
  • [DESCRIPTION]

Interview Protocol

Ask one question at a time. If you are giving options, give a list to choose from.

Phases

Phase 1: Interview
  1. Read the provided file, and ask for the [FILE_NAME] if not provided.
  2. Ask for the [HEADER] for the file.
  3. Ask for a small [DESCRIPTION] of what this process is going to achieve.
  4. Ask for the [STARTER_CHARACTER] emoji. A STARTER_CHARACTER is a marker (usually an emoji) that appears at the beginning of each response to indicate that the context window is intact and rules are being followed. Suggest 5-8 appropriate emoji based on the process topic.
  5. We need a list of steps. Ask for each step in the process, one at a time. If anything is unclear about a step, ask clarifying questions.
  6. Identify any missing steps that would achieve the stated description of the process.
Phase 2: Draft

Create the initial version of the process file, or revise it if it already exists. Ask to review it.

Phase 3: Clarification

Read the draft created in phase 2. Check for inconsistencies, contradictions, or missing information. If any are found, ask clarifying questions one at a time.

Phase 4: Simplification

Review the process file created in phase 2 and simplify. Be as concise as possible.

Examples

For an example of a process file, examine this file itself.

© lexler, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in output_skills/ai/creating-process-files of lexler/skill-factory.

  • SKILL.md
  • credits.md

Open the folder on GitHubat commit 8017333

Compare with similar skills

Creating Process Files 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.

Creating Process Files compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Creating Process Files this skilllexler/skill-factory239—~566Automated safety check: PassApache-2.0
Google Cloud Waf Reliabilitydavila7/claude-code-templates32k—~1.8kAutomated safety check: PassMIT
Google Cloud Waf Reliabilitygoogle/skills21k—~2kAutomated safety check: PassApache-2.0
Gke Reliabilitygoogle/skills21k—~1.8kAutomated safety check: PassApache-2.0
Windows Shell Reliabilitysickn33/agentic-awesome-skills47k2 repos~1kAutomated safety check: PassMIT
Observability And Reliabilitycbrock84/headcount2k—~931Automated safety check: PassMIT

Similar skills

  • Google Cloud Waf Reliability

    davila7/claude-code-templates

    Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework.

    32k GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Official

    Generates guidance for reliability, resilience, availability, redundancy, fault-tolerance, and disaster recovery (DR) for Google Cloud workloads based on the design principles and recommendations in…

    21k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Gke Reliability

    google/skills

    Official

    Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints.

    21k GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Windows Shell Reliability

    sickn33/agentic-awesome-skills

    Reliable command execution on Windows: paths, encoding, and common binary pitfalls.

    47k GitHub starsUsed in 2 repos~1k tokens
    DevOps & CloudAuto-check passed
  • Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure.

    2k GitHub stars~931 tokensUpdated 19 days ago
    DevOps & CloudAuto-check passed
  • Omh Reliability Review

    rlaope/oh-my-hermes

    [omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence.

    3.2k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed

More from lexler/skill-factory

All 25 skills in this repo
  • C4 Architecture Diagrams

    lexler/skill-factory

    Creates C4 model diagrams at every zoom level, from system landscape to code, in ASCII, Mermaid or Structurizr, for designing or documenting software architecture.

    239 GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Launching Agent Teams

    lexler/skill-factory

    Plans and launches Claude Code agent teams with distinct roles, right-sized tasks and detailed spawn prompts, and says when subagents or worktrees fit better.

    239 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Claude Code Statusline Writer

    lexler/skill-factory

    Guides writing and debugging Claude Code status line scripts that read session JSON from stdin and print one line of text.

    239 GitHub stars~872 tokensUpdated 1 mo ago
    Auto-check passed
  • Catalog of obstacles, anti-patterns and patterns for working with AI coding agents, covering context management and reliability, from a published patterns collection.

    239 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Approval Testing Toolkit

    lexler/skill-factory

    Writes snapshot-style approval tests in Python, JavaScript, TypeScript or Java, comparing output against an approved file instead of writing individual assertions.

    239 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Hotspots

    lexler/skill-factory

    Find where a codebase actually costs time by mining its git history (Tornhill hotspot analysis).

    239 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Creating Process Files

What does Creating Process Files do?

Creates process files - text as code instructions for reliable AI workflows. Creating Process Files is an agent skill from lexler/skill-factory. Creates process files - text as code instructions for reliable AI workflows.

When should I use Creating Process Files?

Creating Process Files fits situations like: creating new process files.

How do I install Creating Process Files in Claude Code?

Run `npx skills add lexler/skill-factory --skill creating-process-files -a claude-code`. Or copy the skill folder (output_skills/ai/creating-process-files in lexler/skill-factory) into .claude/skills/creating-process-files in your project. Claude Code loads it when a task matches its description.

How do I install Creating Process Files in Codex?

Run `npx skills add lexler/skill-factory --skill creating-process-files -a codex`. Or copy the skill folder (output_skills/ai/creating-process-files in lexler/skill-factory) into .agents/skills/creating-process-files in your project. Codex loads it when a task matches its description.

Can I use Creating Process Files 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 lexler/skill-factory --skill creating-process-files -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-process-files, .gemini/skills/creating-process-files, .github/skills/creating-process-files and .opencode/skills/creating-process-files in your project.

What does Creating Process Files need to run?

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

Does Creating Process Files 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 Creating Process Files 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 Creating Process Files use?

Creating Process Files 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 Creating Process Files use?

About 566 tokens (SKILL.md is roughly 2.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 Creating Process Files?

Skills that share tags, products or a category with Creating Process Files: Google Cloud Waf Reliability (davila7/claude-code-templates, 32k stars), Google Cloud Waf Reliability (google/skills, 21k stars), Gke Reliability (google/skills, 21k stars) and Windows Shell Reliability (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Creating Process Files?

lexler (a GitHub user) maintains it in lexler/skill-factory, which has 239 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on August 26, 2026.

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