[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78GD9SGGYYBXCGTENJZTFNW":3,"skill-same:01M78GD9SGGYYBXCGTENJZTFNW":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":13,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M78GD9SGGYYBXCGTENJZTFNW","one-three-one-rule",null,"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\u002Fcons, 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.","RESousa01\u002Fbmad-runtime-dev","RESousa01","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F299151629?v=4","01M78G6P63PC4EAYPFT191W6C9","01M78G6P6QE3EY5S0SZRGWYBCS",0,"MIT","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: one-three-one-rule\ndescription: >\n  Structured decision-making framework for technical proposals and trade-off analysis.\n  When the user faces a choice between multiple approaches (architecture decisions,\n  tool selection, refactoring strategies, migration paths), this skill produces a\n  1-3-1 format: one clear problem statement, three distinct options with pros\u002Fcons,\n  and one concrete recommendation with definition of done and implementation plan.\n  Use when the user asks for a \"1-3-1\", says \"give me options\", or needs help\n  choosing between competing approaches.\nplatforms: [linux, macos, windows]\nversion: 1.0.0\nauthor: Willard Moore\nlicense: MIT\ncategory: communication\nmetadata:\n  hermes:\n    tags: [communication, decision-making, proposals, trade-offs]\n---\n\n# 1-3-1 Communication Rule\n\nStructured 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.\n\n## When to Use\n\n- The user explicitly asks for a \"1-3-1\" response.\n- The user says \"give me options\" or \"what are my choices\" for a technical decision.\n- A task has multiple viable approaches with meaningful trade-offs (architecture, tooling, migration strategy).\n- The user needs a proposal they can forward to a team or stakeholder.\n\nDo NOT use for simple questions with one obvious answer, debugging sessions, or tasks where the user has already decided on an approach.\n\n## Procedure\n\n1. **Problem** (one sentence)\n   - State the core decision or desired outcome in a single concise sentence.\n   - Focus on the *what*, not the *how* — no implementation details, tool names, or specific technologies.\n   - Keep it tight. If you need \"and\", you're describing two problems.\n\n2. **Options** (exactly three)\n   - Present three distinct, viable approaches labeled A, B, C.\n   - Each option gets a brief description, pros, and cons.\n   - Options should represent genuinely different strategies, not minor variations of the same approach.\n\n3. **Recommendation** (one option)\n   - State which option you recommend and why, based on the user's context and priorities.\n   - Be direct — this is your professional judgment, not a hedge.\n\n4. **Definition of Done**\n   - List the specific success criteria for the recommended option.\n   - These are concrete, verifiable outcomes — not vague aspirations.\n   - If the user picks a different option, revise this section to match.\n\n5. **Implementation Plan**\n   - Concrete steps to execute the recommended option.\n   - Include specific commands, tools, or actions where applicable.\n   - If the user picks a different option, revise this section to match.\n\n## Verification\n\n- Response has exactly one Problem sentence.\n- Response has exactly three Options (A, B, C) with pros and cons for each.\n- Response has a single Recommendation that picks one option with reasoning.\n- Definition of Done and Implementation Plan align with the recommended option.\n- If the user selects a different option, Recommendation, DoD, and Implementation Plan update accordingly.\n\n## Example\n\nUser: \"Give me a 1-3-1 for adding retry logic to our API client.\"\n\nAgent:\n\n**Problem:** API calls to external services fail intermittently under load and need graceful retry handling.\n\n**Options:**\n\n- **Option A: Exponential backoff with jitter in a shared utility.**\n  Pros: Simple, well-understood pattern; single implementation shared across all callers.\n  Cons: No circuit-breaking; callers still block during retries.\n\n- **Option B: Retry library (tenacity) as a decorator on each endpoint call.**\n  Pros: Configurable per-endpoint; built-in support for circuit breakers and rate limits.\n  Cons: Adds a dependency; decorator pattern can obscure control flow.\n\n- **Option C: Queue-based async retry with dead letter handling.**\n  Pros: Non-blocking; failed calls are tracked and replayable; scales well.\n  Cons: Significant complexity increase; requires a queue backend; overkill for low-volume services.\n\n**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.\n\n**Definition of Done:**\n- `api_retry()` utility handles transient HTTP errors (429, 502, 503, 504).\n- Retries up to 3 times with exponential backoff and jitter.\n- All external API calls route through the retry utility.\n- Logs each retry attempt with endpoint and attempt number.\n- Tests cover retry exhaustion, immediate success, and transient-then-success scenarios.\n\n**Implementation Plan:**\n1. Create `utils\u002Fapi_retry.py` with configurable max retries, base delay, and retryable status codes.\n2. Add jitter using `random.uniform(0, base_delay)` to prevent thundering herd.\n3. Wrap existing API calls in `api_client.py` with the retry utility.\n4. Add unit tests mocking HTTP responses for each retry scenario.\n5. Verify under load with a simple stress test against a flaky endpoint mock.\n","# 1-3-1 Communication Rule\n\nStructured 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.\n\n## When to Use\n\n- The user explicitly asks for a \"1-3-1\" response.\n- The user says \"give me options\" or \"what are my choices\" for a technical decision.\n- A task has multiple viable approaches with meaningful trade-offs (architecture, tooling, migration strategy).\n- The user needs a proposal they can forward to a team or stakeholder.\n\nDo NOT use for simple questions with one obvious answer, debugging sessions, or tasks where the user has already decided on an approach.\n\n## Procedure\n\n1. **Problem** (one sentence)\n   - State the core decision or desired outcome in a single concise sentence.\n   - Focus on the *what*, not the *how* — no implementation details, tool names, or specific technologies.\n   - Keep it tight. If you need \"and\", you're describing two problems.\n\n2. **Options** (exactly three)\n   - Present three distinct, viable approaches labeled A, B, C.\n   - Each option gets a brief description, pros, and cons.\n   - Options should represent genuinely different strategies, not minor variations of the same approach.\n\n3. **Recommendation** (one option)\n   - State which option you recommend and why, based on the user's context and priorities.\n   - Be direct — this is your professional judgment, not a hedge.\n\n4. **Definition of Done**\n   - List the specific success criteria for the recommended option.\n   - These are concrete, verifiable outcomes — not vague aspirations.\n   - If the user picks a different option, revise this section to match.\n\n5. **Implementation Plan**\n   - Concrete steps to execute the recommended option.\n   - Include specific commands, tools, or actions where applicable.\n   - If the user picks a different option, revise this section to match.\n\n## Verification\n\n- Response has exactly one Problem sentence.\n- Response has exactly three Options (A, B, C) with pros and cons for each.\n- Response has a single Recommendation that picks one option with reasoning.\n- Definition of Done and Implementation Plan align with the recommended option.\n- If the user selects a different option, Recommendation, DoD, and Implementation Plan update accordingly.\n\n## Example\n\nUser: \"Give me a 1-3-1 for adding retry logic to our API client.\"\n\nAgent:\n\n**Problem:** API calls to external services fail intermittently under load and need graceful retry handling.\n\n**Options:**\n\n- **Option A: Exponential backoff with jitter in a shared utility.**\n  Pros: Simple, well-understood pattern; single implementation shared across all callers.\n  Cons: No circuit-breaking; callers still block during retries.\n\n- **Option B: Retry library (tenacity) as a decorator on each endpoint call.**\n  Pros: Configurable per-endpoint; built-in support for circuit breakers and rate limits.\n  Cons: Adds a dependency; decorator pattern can obscure control flow.\n\n- **Option C: Queue-based async retry with dead letter handling.**\n  Pros: Non-blocking; failed calls are tracked and replayable; scales well.\n  Cons: Significant complexity increase; requires a queue backend; overkill for low-volume services.\n\n**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.\n\n**Definition of Done:**\n- `api_retry()` utility handles transient HTTP errors (429, 502, 503, 504).\n- Retries up to 3 times with exponential backoff and jitter.\n- All external API calls route through the retry utility.\n- Logs each retry attempt with endpoint and attempt number.\n- Tests cover retry exhaustion, immediate success, and transient-then-success scenarios.\n\n**Implementation Plan:**\n1. Create `utils\u002Fapi_retry.py` with configurable max retries, base delay, and retryable status codes.\n2. Add jitter using `random.uniform(0, base_delay)` to prevent thundering herd.\n3. Wrap existing API calls in `api_client.py` with the retry utility.\n4. Add unit tests mocking HTTP responses for each retry scenario.\n5. Verify under load with a simple stress test against a flaky endpoint mock.\n",{"name":5,"author":23,"license":14,"version":24,"category":25,"metadata":26,"platforms":32,"description":36},"Willard Moore","1.0.0","communication",{"hermes":27},{"tags":28},[25,29,30,31],"decision-making","proposals","trade-offs",[33,34,35],"linux","macos","windows","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\u002Fcons, 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.\n","main","f6a8453b945427ad778127c99f3da279c47a2220","bmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev","https:\u002F\u002Fgithub.com\u002FRESousa01","2026-10-19 13:01:14",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add RESousa01\u002Fbmad-runtime-dev --skill one-three-one-rule",{"tool":49,"command":50},"bunx","bunx skills add RESousa01\u002Fbmad-runtime-dev --skill one-three-one-rule",{"tool":52,"command":53},"pnpm","pnpm dlx skills add RESousa01\u002Fbmad-runtime-dev --skill one-three-one-rule","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule\u002FSKILL.md",true,[],[58,67,75,82,89,96],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M78H3BBP6055J6C6Y0H85EFP","skill-creator","Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fopenclaw-main\u002Fopenclaw-main\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fopenclaw-main\u002Fopenclaw-main\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M78H0B17WY9EQRPAV9G55Y2D","prose","OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fopenclaw-main\u002Fopenclaw-main\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fopenclaw-main\u002Fopenclaw-main\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M78GYV3AEHB5ZQ8XH131F9HE","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M78GYQ03NRD6F6KVBDX8STSJ","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M78GYMHFYT1W2W0RN48E49BQ","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M78GYF9P7VZ8YJCVJPYS6KER","simplify-code","Parallel 3-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002FRESousa01\u002Fbmad-runtime-dev\u002Fblob\u002Fmain\u002Fbmad-runtime-lib\u002F_source_review\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[]]