New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

One Three One Rule

by Tommy-yw in Tommy-yw/RunbookHermes

Structured decision-making framework for technical proposals and trade-off analysis.

MITAuto-check passedAgent Workflows

Install One Three One Rule

skills CLI
$ npx skills add Tommy-yw/RunbookHermes --skill one-three-one-rule -a claude-code

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

GitHub CLI
$ gh skill install Tommy-yw/RunbookHermes one-three-one-rule --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/Tommy-yw/RunbookHermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/optional-skills/communication/one-three-one-rule .claude/skills/one-three-one-rule && 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
one-three-one-rule
GitHub stars
546
Used in
3 other repos
Token cost
~1.3k tokens
SKILL.md length
599 words
Files
1
Skills in repo
38
Repo updated
First seen
Licence
MIT

At a glance

Structured decision-making framework for technical proposals and trade-off analysis.

  • Works in 5 steps: Problem (one sentence) → Options (exactly three) → Recommendation (one option) → …
  • Faces a choice between multiple approaches (architecture decisions
  • SKILL.md covers When to Use, Procedure, Verification and Example
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

One Three One Rule is an agent skill from Tommy-yw/RunbookHermes. Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing…

Its SKILL.md is about 1.3k 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 Agent Workflows, covering Planning, Proposals and quotes and Refactoring. The repository describes itself as: Hermes-native AIOps agent for evidence-driven incident response, approval-gated remediation, and runbook learning. The licence is MIT.

When your agent uses it

  • Faces a choice between multiple approaches (architecture decisions
  • Refactoring strategies
  • Migration paths)
  • This skill produces a 1-3-1 format: one clear problem statement

Example prompts

  • “, says”
  • “/one-three-one-rule”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Problem (one sentence)
  2. Options (exactly three)
  3. Recommendation (one option)
  4. Definition of Done
  5. Implementation Plan

What it can do on your machine

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

One Three One Rule loads about 1.3k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 599 words of instructions outside code blocks.

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

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 Tommy-yw/RunbookHermes at commit 7fd2b9a, republished under its MIT licence (© Tommy-yw). 599 words, ~1,255 tokens.

Download SKILL.mdSave it as .claude/skills/one-three-one-rule/SKILL.md (or your agent's skills folder).
name
one-three-one-rule
description
Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.
version
1.0.0
author
Willard Moore
license
MIT
category
communication

1-3-1 Communication Rule

Structured decision-making format for when a task has multiple viable approaches and the user needs a clear recommendation. Produces a concise problem framing, three options with trade-offs, and an actionable plan for the recommended path.

When to Use

  • The user explicitly asks for a "1-3-1" response.
  • The user says "give me options" or "what are my choices" for a technical decision.
  • A task has multiple viable approaches with meaningful trade-offs (architecture, tooling, migration strategy).
  • The user needs a proposal they can forward to a team or stakeholder.

Do NOT use for simple questions with one obvious answer, debugging sessions, or tasks where the user has already decided on an approach.

Procedure

  1. Problem (one sentence)

    • State the core decision or desired outcome in a single concise sentence.
    • Focus on the what, not the how — no implementation details, tool names, or specific technologies.
    • Keep it tight. If you need "and", you're describing two problems.

  2. Options (exactly three)

    • Present three distinct, viable approaches labeled A, B, C.
    • Each option gets a brief description, pros, and cons.
    • Options should represent genuinely different strategies, not minor variations of the same approach.

  3. Recommendation (one option)

    • State which option you recommend and why, based on the user's context and priorities.
    • Be direct — this is your professional judgment, not a hedge.

  4. Definition of Done

    • List the specific success criteria for the recommended option.
    • These are concrete, verifiable outcomes — not vague aspirations.
    • If the user picks a different option, revise this section to match.

  5. Implementation Plan

    • Concrete steps to execute the recommended option.
    • Include specific commands, tools, or actions where applicable.
    • If the user picks a different option, revise this section to match.

Verification

  • Response has exactly one Problem sentence.
  • Response has exactly three Options (A, B, C) with pros and cons for each.
  • Response has a single Recommendation that picks one option with reasoning.
  • Definition of Done and Implementation Plan align with the recommended option.
  • If the user selects a different option, Recommendation, DoD, and Implementation Plan update accordingly.
Show full SKILL.md (260 more words)Show less

Example

User: "Give me a 1-3-1 for adding retry logic to our API client."

Agent:

Problem: API calls to external services fail intermittently under load and need graceful retry handling.

Options:

  • Option A: Exponential backoff with jitter in a shared utility. Pros: Simple, well-understood pattern; single implementation shared across all callers. Cons: No circuit-breaking; callers still block during retries.

  • Option B: Retry library (tenacity) as a decorator on each endpoint call. Pros: Configurable per-endpoint; built-in support for circuit breakers and rate limits. Cons: Adds a dependency; decorator pattern can obscure control flow.

  • Option C: Queue-based async retry with dead letter handling. Pros: Non-blocking; failed calls are tracked and replayable; scales well. Cons: Significant complexity increase; requires a queue backend; overkill for low-volume services.

Recommendation: Option A. The call volume doesn't justify queue infrastructure, and a shared utility with exponential backoff + jitter covers the failure mode cleanly without new dependencies.

Definition of Done:

  • api_retry() utility handles transient HTTP errors (429, 502, 503, 504).
  • Retries up to 3 times with exponential backoff and jitter.
  • All external API calls route through the retry utility.
  • Logs each retry attempt with endpoint and attempt number.
  • Tests cover retry exhaustion, immediate success, and transient-then-success scenarios.

Implementation Plan:

  1. Create utils/api_retry.py with configurable max retries, base delay, and retryable status codes.
  2. Add jitter using random.uniform(0, base_delay) to prevent thundering herd.
  3. Wrap existing API calls in api_client.py with the retry utility.
  4. Add unit tests mocking HTTP responses for each retry scenario.
  5. Verify under load with a simple stress test against a flaky endpoint mock.

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

Files

Just SKILL.md in optional-skills/communication/one-three-one-rule of Tommy-yw/RunbookHermes.

Open the folder on GitHubat commit 7fd2b9a

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in Tommy-yw/RunbookHermes, which our catalogue first saw on October 7, 2026.

Compare with similar skills

One Three One Rule 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.

One Three One Rule compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
One Three One Rule this skillTommy-yw/RunbookHermes5463 repos~1.3kAutomated safety check: PassMIT
Improvefossasia/eventyay-interpretation1.6k10 repos~3.7kAutomated safety check: WarnMIT
Designsynnaxlabs/synnax128—~4.5kAutomated safety check: PassCustom licence
Speckdlbs/kandev912—~2.1kAutomated safety check: PassAGPL-3.0
Blueprint Refactor Surveyreceptron/mulmoterminal237—~1.3kAutomated safety check: PassMIT
Workflow Orchestrationvxcozy/workflow-orchestration116—~1kAutomated safety check: PassMIT

Similar skills

  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Agent WorkflowsAuto-check: warnings

  • Design

    synnaxlabs/synnax

    Process and hard rules for designing and planning complex new features, refactors, and re-architectures.

    128 GitHub stars~4.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Spec

    kdlbs/kandev

    Create or update Kandev product requirements and system-design documents before implementation.

    912 GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Blueprint Refactor Survey

    receptron/mulmoterminal

    Find what is worth tidying in this repository, measure each candidate's value and risk, and write a plan the person approves — including what to leave alone and why.

    237 GitHub stars~1.3k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Workflow Orchestration

    vxcozy/workflow-orchestration

    Disciplined task execution with planning, verification, and self-improvement loops.

    116 GitHub stars~1k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed

  • Plan Writing

    xenitV1/Antigravity-Workflows

    Structured task planning with clear breakdowns, dependencies, and verification criteria.

    130 GitHub starsUsed in 8 repos~994 tokens
    DevelopmentAuto-check passed

More from Tommy-yw/RunbookHermes

All 38 skills in this repo

  • Fastmcp

    Tommy-yw/RunbookHermes

    Build, test, inspect, install, and deploy MCP servers with FastMCP in Python.

    546 GitHub starsUsed in 3 repos~2.1k tokens
    Auto-check passed

  • Drug Discovery

    Tommy-yw/RunbookHermes

    Pharmaceutical research assistant for drug discovery workflows.

    546 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Youtube Content

    Tommy-yw/RunbookHermes

    Fetch YouTube video transcripts and transform them into structured content (chapters, summaries, threads, blog posts).

    546 GitHub starsUsed in 1 repo~785 tokens
    Auto-check passed

  • Oss Forensics

    Tommy-yw/RunbookHermes

    Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories.

    546 GitHub starsUsed in 3 repos~5k tokens
    Auto-check passed

  • P5js

    Tommy-yw/RunbookHermes

    Production pipeline for interactive and generative visual art using p5.js.

    546 GitHub starsUsed in 1 repo~6.8k tokens
    Auto-check passed

  • Touchdesigner MCP

    Tommy-yw/RunbookHermes

    Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals.

    546 GitHub starsUsed in 2 repos~3.4k tokens
    Auto-check passed

Categories

Questions about One Three One Rule

What does One Three One Rule do?

Structured decision-making framework for technical proposals and trade-off analysis. One Three One Rule is an agent skill from Tommy-yw/RunbookHermes. Structured decision-making framework for technical proposals and trade-off analysis.

When should I use One Three One Rule?

One Three One Rule fits situations like: faces a choice between multiple approaches (architecture decisions; refactoring strategies; migration paths); this skill produces a 1-3-1 format: one clear problem statement.

How do I install One Three One Rule in Claude Code?

Run `npx skills add Tommy-yw/RunbookHermes --skill one-three-one-rule -a claude-code`. Or copy the skill folder (optional-skills/communication/one-three-one-rule in Tommy-yw/RunbookHermes) into .claude/skills/one-three-one-rule in your project. Claude Code loads it when a task matches its description.

How do I install One Three One Rule in Codex?

Run `npx skills add Tommy-yw/RunbookHermes --skill one-three-one-rule -a codex`. Or copy the skill folder (optional-skills/communication/one-three-one-rule in Tommy-yw/RunbookHermes) into .agents/skills/one-three-one-rule in your project. Codex loads it when a task matches its description.

Can I use One Three One Rule 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 Tommy-yw/RunbookHermes --skill one-three-one-rule -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/one-three-one-rule, .gemini/skills/one-three-one-rule, .github/skills/one-three-one-rule and .opencode/skills/one-three-one-rule in your project.

What does One Three One Rule need to run?

SKILL.md names no scripts, command-line tools or credentials: One Three One Rule is instructions for the agent only.

Does One Three One Rule 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 One Three One Rule 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 One Three One Rule use?

One Three One Rule is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does One Three One Rule use?

About 1.3k tokens (SKILL.md is roughly 5k 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 One Three One Rule?

Skills that share tags, products or a category with One Three One Rule: Improve (fossasia/eventyay-interpretation, 1.6k stars), Design (synnaxlabs/synnax, 128 stars), Spec (kdlbs/kandev, 912 stars) and Blueprint Refactor Survey (receptron/mulmoterminal, 237 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains One Three One Rule?

Tommy-yw (a GitHub user) maintains it in Tommy-yw/RunbookHermes, which has 546 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on May 18, 2026.

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