[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78DRAV3ACGW7GTVGDAXMZQS":3,"skill-same:01M78DRAV3ACGW7GTVGDAXMZQS":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M78DRAV3ACGW7GTVGDAXMZQS","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.","pvbang\u002Fnexus","pvbang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89725712?v=4","01M78B6R1DXZZBTN9G0XXBBE0A","Phan Văn Bằng","01M78B6R2T4DYQ9ZY4GJR0Q3V4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\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.\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":24,"license":15,"version":25,"category":26,"metadata":27,"description":33},"Willard Moore","1.0.0","communication",{"hermes":28},{"tags":29},[26,30,31,32],"decision-making","proposals","trade-offs","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","a0559bb2eb5ae47d603efe32afe4589f77bf4ded","src\u002Fopen-source\u002Fhermes-agent\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus","https:\u002F\u002Fgithub.com\u002Fpvbang","pvbang.github.io\u002Fcv","\u003C\u002F> It's a pleasure to meet you","2026-11-13 16:52:49",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add pvbang\u002Fnexus --skill one-three-one-rule",{"tool":48,"command":49},"bunx","bunx skills add pvbang\u002Fnexus --skill one-three-one-rule",{"tool":51,"command":52},"pnpm","pnpm dlx skills add pvbang\u002Fnexus --skill one-three-one-rule","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Foptional-skills\u002Fcommunication\u002Fone-three-one-rule\u002FSKILL.md",true,[],[57,66,74,81,88,95],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M78EFV6FYHV11YKAKYXPND85","skill-creator","Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references\u002F or scripts\u002F, removing stale content, validating against the AgentSkills spec). Triggers on phrases like \"create a skill\", \"author a skill\", \"tidy up a skill\", \"improve this skill\", \"review the skill\", \"clean up the skill\", \"audit the skill\".","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78EC37DFKY5X6RFQ6XPE9EY","prose","OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78E9C2RKT5BJ8ZR9KZTNS2A","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78E98QY8PH80R7QN1P8NMTH","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78E93DGFNKP1WZ9WJ9S9N7H","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M78E8ZM4CER22PJT0WJ1RWMJ","subagent-driven-development","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[]]