Atmet-Skill

atmet-skill is a reusable Codex/Claude-compatible skill project for turning manual business workflows into practical automation plans, implementation artifacts, and safe rollout checklists.

What This Skill Does

This skill helps teams:

• Discover and map current manual workflows.
• Identify automation opportunities and safe manual checkpoints.
• Recommend tools and implementation paths.
• Generate process documentation, automation plans, and QA controls.
• Produce reusable templates for delivery and team alignment.

Who It Is For

• Developers building internal automations.
• Consultants designing process improvements for clients.
• Operations, finance, marketing, and reporting teams.
• Product and delivery teams standardizing recurring workflows.

When To Use It

Use this skill when you need to analyze, automate, document, or improve:

• Reporting workflows
• Approval workflows
• Data validation workflows
• Onboarding/offboarding processes
• Internal operations handoffs
• Client communication processes

Do not use it for unrelated coding tasks that are not tied to workflow/process automation.

What It Can Generate

• Process briefs
• Workflow maps
• Automation plans
• Technical requirements
• Data mapping outlines
• Message/email drafts
• QA checklists
• Rollout plans
• Risk and controls checklists

Installation Options

Option 1: Global Install

npm install -g atmet-skill
atmet-skill install

Option 2: Run With NPX

npx atmet-skill install

Option 3: Manual Install

1. Copy skills/Atmet-Skill into your local skills directory.
2. For Codex, skills can be loaded from user-level or repo-level directories depending on your setup.
3. For Claude/Claude Code environments, you may need to upload/package the skill folder based on your local agent runtime.

Note: The installer copies files into common local skill folders. If your agent uses a different path, choose the custom path option.

CLI Commands

atmet-skill install
atmet-skill uninstall
atmet-skill validate
atmet-skill help

Usage With Codex

1. Install/copy the skill folder into your Codex skills directory.
2. Start Codex in a repo where skill loading is enabled.
3. Prompt with a workflow automation request, for example:

Analyze our monthly client reporting workflow and create a safe automation plan with QA and rollout steps.

Usage With Claude

1. Add the Atmet-Skill skill folder into the skill path expected by your Claude/Claude Code setup.
2. Ensure the SKILL.md file and references/ directory are included.
3. Prompt with a business process automation request.

Customizing For A Company

1. Start from references/company-profile-template.md.
2. Fill your company tools, KPIs, approvals, and risk areas.
3. Attach or paste that profile in your workflow request.
4. The skill will adapt recommendations to your profile.

An example profile is included at:

• references/example-company-profile-regional-services.md (example only, optional)

Uninstall

atmet-skill uninstall

The uninstaller is interactive and only removes folders named Atmet-Skill after confirmation.

Security And Privacy Notes

• No external APIs are called by installer scripts.
• No telemetry or data collection is performed.
• No admin/sudo privileges are required.
• Review generated plans before applying automation to production systems.

Example Prompts

• "Map our invoice reminder process and propose a low-risk automation with approval gates."
• "Convert our weekly KPI reporting steps into a scheduled automation plan and QA checklist."
• "Design a validation workflow for supplier data with exception handling and audit logging."
• "Create onboarding workflow documentation and implementation tasks for HR + IT handoff."

Repository Structure

process-automation-architect-skill/
  README.md
  LICENSE
  package.json
  install.js
  uninstall.js
  .gitignore
  .codex-plugin/
    plugin.json
  skills/
    Atmet-Skill/
      SKILL.md
      references/
      scripts/
      assets/
  tests/

Plugin note: .codex-plugin/plugin.json points to ../skills/ relative to the manifest. Some marketplace packaging layouts may require path adjustment.

Validation

npm run validate
npm test

Both commands use local files only.