common-workflow-writing
Rules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 2
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 6fdf3d412dbba42b… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Workflow Writing Standard
Priority: P0 (CRITICAL)
Core Rules
- Templates, not examples: Workflows define structure, not pre-filled data. agent generates data at runtime.
- No example rows in tables: Include headers + 1 skeleton row only. Never populate with fake data.
- No prose explanations: If bullet or command achieves same result, delete paragraph.
- No pre-answered questions: Don't document what agent will output — let it output it.
- Merge sequential steps: If two steps always happen together, they one step.
Size Limits
| File type | Limit | If exceeded |
|---|---|---|
Workflow .md | 80 lines | Extract detail to references/ |
| SKILL.md | 100 lines | Extract examples to references/ |
| Table rows | 8 | Extract to references/ |
| Inline code block | 10 lines | Extract to references/ |
Workflow Structure (Required order)
1. Goal (1 sentence)
2. Steps (imperative verb → command or checklist)
3. Output template (headers only, no pre-filled rows)
Anti-Patterns
- No verbose step preambles:
"Before we start, it's important to understand..."→ Delete - No pre-filled report rows:
| Security | P0 | ✅ PASS | CLIENT_ID moved to env |→ Delete - No repeated examples: Same concept shown twice in different formats → Keep one
- No "How to X" sections: step instruction
- No caution blocks for obvious rules: Reserve
> ⚠️for genuinely non-obvious risks - Portable output contracts: Use
feature_status, missing evidence, decision needed, and adapter-neutral language; avoid runtime-specific tool names, chat channels, containers, and mount paths in canonical workflows.
Quick Self-Check Before Saving
- Can agent reconstruct any removed content at runtime from context? If yes → remove it
- every table row real structure, not example data?
- there any paragraphs bullet list could replace?
- Would cutting this in half still give agent enough to act on?
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- 80 lines
- delete
Files
2- SKILL.md
153063fb1a2.6 KB - evals/evals.json
b9e81f40364.7 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.