Workflow Writing Standard

Enforce conciseness and token efficiency in workflow and skill file creation.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/ntluong95/agent-skills-statistics --skill workflow-writing-standard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Workflow Writing Standard
Source: https://github.com/ntluong95/agent-skills-statistics/tree/main/.github/skills/common/workflow-writing
Command: npx skills add https://github.com/ntluong95/agent-skills-statistics --skill workflow-writing-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that workflow and skill files are written concisely and efficiently, preventing over-building and reducing the need for costly optimization passes.

Core Features & Use Cases

  • Conciseness Enforcement: Guides users to create templates rather than examples, avoiding unnecessary prose and pre-filled data.
  • Size Limit Adherence: Provides clear limits for file size, table rows, and code blocks, with instructions on how to handle content that exceeds these limits.
  • Anti-Pattern Identification: Lists common pitfalls to avoid, such as verbose preambles and repeated examples.
  • Use Case: When creating a new workflow for an AI agent, this Skill's guidelines help ensure the workflow is clear, actionable, and avoids unnecessary verbosity, making it easier for the agent to process and execute.

Quick Start

Follow the provided rules and anti-patterns to write efficient workflow and skill files.

Frequently Asked Questions about Workflow Writing Standard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write concise and token-efficient AI agent workflows?

To write concise AI agent workflows, use templates instead of examples, eliminate prose, merge sequential steps, and adhere to specific file, table, and code block size limits.

What are common anti-patterns in prompt engineering and skill file creation?

Common anti-patterns in skill file creation include verbose preambles, repeated examples, and pre-filled data, which reduce token efficiency and complicate AI agent processing.

How do I handle size limits when creating workflow files?

When workflow files exceed size limits, you should follow specific guidelines for handling content overages in file sizes, table rows, and code blocks to maintain token efficiency.

Why does my AI workflow require an optimization pass to reduce token usage?

Your AI workflow likely requires optimization because it contains unnecessary verbosity, such as pre-filled example data and prose, rather than using token-efficient templates.

Can I use pre-filled example data when creating skill files for AI agents?

You should avoid pre-filled example data when creating skill files. Creating reusable templates ensures conciseness, improves token efficiency, and prevents over-building.

What is the best way to structure prompt engineering workflows for token efficiency?

The best way to structure prompt engineering workflows is to merge sequential steps, avoid verbose preambles, and enforce strict size limits for files, tables, and code blocks.