Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Methodology for systematically designing and generating CLI tool argument parser structures.
$ npx skills add revfactory/harness-100 --skill arg-parser-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 arg-parser-generator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/40-cli-tool-builder/.claude/skills/arg-parser-generator .claude/skills/arg-parser-generator && rm -rf skills-srcUse ~/.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/
Install the "arg-parser-generator" agent skill from https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generator into .claude/skills/arg-parser-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arg-parser-generator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generatorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add revfactory/harness-100 --skill arg-parser-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 arg-parser-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/40-cli-tool-builder/.claude/skills/arg-parser-generator .agents/skills/arg-parser-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "arg-parser-generator" agent skill from https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generator into .agents/skills/arg-parser-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arg-parser-generator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill arg-parser-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 arg-parser-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/40-cli-tool-builder/.claude/skills/arg-parser-generator .cursor/skills/arg-parser-generator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "arg-parser-generator" agent skill from https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generator into .cursor/skills/arg-parser-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arg-parser-generator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/revfactory/harness-100.git --path en/40-cli-tool-builder/.claude/skills/arg-parser-generator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add revfactory/harness-100 --skill arg-parser-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 arg-parser-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/40-cli-tool-builder/.claude/skills/arg-parser-generator .gemini/skills/arg-parser-generator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "arg-parser-generator" agent skill from https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generator into .gemini/skills/arg-parser-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arg-parser-generator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install revfactory/harness-100 arg-parser-generatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add revfactory/harness-100 --skill arg-parser-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/40-cli-tool-builder/.claude/skills/arg-parser-generator .github/skills/arg-parser-generator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "arg-parser-generator" agent skill from https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generator into .github/skills/arg-parser-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arg-parser-generator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill arg-parser-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 arg-parser-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/40-cli-tool-builder/.claude/skills/arg-parser-generator .opencode/skills/arg-parser-generator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "arg-parser-generator" agent skill from https://github.com/revfactory/harness-100/tree/main/en/40-cli-tool-builder/.claude/skills/arg-parser-generator into .opencode/skills/arg-parser-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arg-parser-generator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
arg-parser-generatorMethodology for systematically designing and generating CLI tool argument parser structures.
Arg Parser Generator is an agent skill from revfactory/harness-100. Methodology for systematically designing and generating CLI tool argument parser structures. Use this skill for 'CLI argument design', 'option structure', 'subcommand design', 'argument parser generation', 'help text design', and other CLI argument system design tasks. Note: GUI interface design and TUI framework integration are outside the scope of this skill.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering API design. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python, javascript and go).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Arg Parser Generator loads about 1.2k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 150 words of instructions outside code blocks.
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.
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.
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 150 words, ~1,195 tokens.
.claude/skills/arg-parser-generator/SKILL.md (or your agent's skills folder).A skill that enhances argument parser design for the command-designer and core-developer.
| Type | Format | Example |
|---|---|---|
| Positional argument | <arg> | convert input.json |
| Required option | --name VALUE | --output out.yaml |
| Optional option | [--name VALUE] | [--indent 2] |
| Flag | [--flag] | [--verbose] |
| Multiple values | --name V1 V2 | --files a.txt b.txt |
| Enum | --type {a,b,c} | --format {json,yaml} |
| Environment variable | $ENV_VAR | $API_KEY |
mytool create <resource> [options]
mytool list [resource] [--filter]
mytool get <id> [--format]
mytool update <id> [options]
mytool delete <id> [--force]mytool user list
mytool user create --name "name"
mytool project deploy --env prodmytool parse input.json | mytool transform --schema s.yaml | mytool output1. Short/long option pairs: -o / --output
2. Boolean + negation: --color / --no-color
3. Consistent nouns: --output-dir (not verbs like --write-to)
4. Abbreviation when unambiguous: --config -> --cfg
Prohibited patterns:
- -h (reserved for help), -V (reserved for version)
- Uppercase short options (-A, -B) — cause confusion
- Overly long options (--output-directory-path)import typer
from typing import Optional
from enum import Enum
app = typer.Typer(help="File conversion CLI")
class Format(str, Enum):
json = "json"
yaml = "yaml"
toml = "toml"
@app.command()
def convert(
input_file: str = typer.Argument(..., help="Input file"),
from_format: Format = typer.Option(..., "--from", "-f", help="Input format"),
to_format: Format = typer.Option(..., "--to", "-t", help="Output format"),
output: Optional[str] = typer.Option(None, "--output", "-o", help="Output file"),
indent: int = typer.Option(2, "--indent", help="Indentation"),
verbose: bool = typer.Option(False, "--verbose", "-v", help="Verbose logging"),
):
"""Convert file formats."""
...
if __name__ == "__main__":
app()const { Command } = require('commander');
const program = new Command();
program
.name('mytool')
.description('File conversion CLI')
.version('1.0.0');
program
.command('convert <input>')
.option('-f, --from <format>', 'Input format', 'json')
.option('-t, --to <format>', 'Output format', 'yaml')
.option('-o, --output <file>', 'Output file')
.action((input, options) => { ... });
program.parse();var convertCmd = &cobra.Command{
Use: "convert [input]",
Short: "Convert file formats",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
from, _ := cmd.Flags().GetString("from")
to, _ := cmd.Flags().GetString("to")
// ...
return nil
},
}
func init() {
convertCmd.Flags().StringP("from", "f", "json", "Input format")
convertCmd.Flags().StringP("to", "t", "yaml", "Output format")
convertCmd.Flags().StringP("output", "o", "", "Output file")
}Usage: mytool <command> [options]
Commands:
convert Convert file formats
validate Validate file syntax
diff Compare two files
Options:
-h, --help Show help
-V, --version Show version
-v, --verbose Verbose output
--no-color Disable colors
Examples:
mytool convert input.json --to yaml
mytool validate schema.json data.json
Environment:
MYTOOL_CONFIG Config file path| Code | Meaning | Usage |
|---|---|---|
| 0 | Success | Normal completion |
| 1 | General error | Runtime error |
| 2 | Argument error | Invalid argument/option |
| 126 | Permission denied | File access denied |
| 127 | Dependency missing | Required tool not installed |
| 130 | User interrupt | Ctrl+C |
© revfactory, 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
Just SKILL.md in en/40-cli-tool-builder/.claude/skills/arg-parser-generator of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Arg Parser Generator 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Arg Parser Generator this skillrevfactory/harness-100 | 1.3k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Go Pedantrychromedp/chromedp | 13k | — | ~3.7k | Automated safety check: Pass | MIT | |
| LangBot Core Developmentlangbot-app/LangBot | 18k | — | ~1.4k | Automated safety check: Notes | Apache-2.0 | |
| Breaking Change Analysisruby-git/ruby-git | 1.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Atomui Control OptimizationAtomUI/AtomUI | 842 | — | ~3.4k | Automated safety check: Pass | LGPL-3.0 | |
| Go Standardsasymmetric-research/solana-exporter | 133 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
langbot-app/LangBot
Covers developing the LangBot core backend and web UI: dev setup, repo layout, API auth types, adding endpoints, migrations and keeping the MCP server in step.
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
AtomUI/AtomUI
A skill your agent uses when optimizing, refactoring, reviewing, or fixing AtomUI controls, including control API contracts, member layout, file splitting, lifecycle, AXAML structure, correctness…
asymmetric-research/solana-exporter
Idiomatic Go conventions — naming, error handling, concurrency, interfaces, testing, and API design.
sketch7/FluentlyHttpClient
Write modern, high-performance C code using records, pattern matching, value objects, async/await, Span<T/Memory<T, and best-practice API design patterns.
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
revfactory/harness-100
A systematic checklist generation engine for compliance audits.
Categories
Methodology for systematically designing and generating CLI tool argument parser structures. Arg Parser Generator is an agent skill from revfactory/harness-100. Methodology for systematically designing and generating CLI tool argument parser structures.
Arg Parser Generator fits situations like: CLI argument design; option structure; subcommand design; argument parser generation.
Run `npx skills add revfactory/harness-100 --skill arg-parser-generator -a claude-code`. Or copy the skill folder (en/40-cli-tool-builder/.claude/skills/arg-parser-generator in revfactory/harness-100) into .claude/skills/arg-parser-generator in your project. Claude Code loads it when a task matches its description.
Run `npx skills add revfactory/harness-100 --skill arg-parser-generator -a codex`. Or copy the skill folder (en/40-cli-tool-builder/.claude/skills/arg-parser-generator in revfactory/harness-100) into .agents/skills/arg-parser-generator in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add revfactory/harness-100 --skill arg-parser-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/arg-parser-generator, .gemini/skills/arg-parser-generator, .github/skills/arg-parser-generator and .opencode/skills/arg-parser-generator in your project.
Going by SKILL.md and its folder, Arg Parser Generator needs credentials named API_KEY. Our summary lists: Python 3; Node.js; A credential in API_KEY.
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.
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.
Arg Parser Generator 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.
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Arg Parser Generator: Go Pedantry (chromedp/chromedp, 13k stars), LangBot Core Development (langbot-app/LangBot, 18k stars), Breaking Change Analysis (ruby-git/ruby-git, 1.8k stars) and Atomui Control Optimization (AtomUI/AtomUI, 842 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,290 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.