{
  "schemaVersion": "1.0",
  "item": {
    "slug": "decide",
    "name": "Decide",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/ivangdavila/decide",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/decide",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/decide",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=decide",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "components.md",
      "confidence.md",
      "exceptions.md",
      "memory-template.md",
      "migration.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/decide"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/decide",
    "agentPageUrl": "https://openagent3.xyz/skills/decide/agent",
    "manifestUrl": "https://openagent3.xyz/skills/decide/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/decide/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Architecture",
        "body": "Decision state lives in ~/decide/. If that folder is missing or empty, run setup.md.\n\n~/decide/\n├── memory.md        # Durable decision rules, approval boundaries, and confirmed defaults\n├── decisions.md     # Major decisions with question, components, chosen option, and outcome\n└── domains/         # Domain-specific decision components, overrides, and exceptions"
      },
      {
        "title": "When to Use",
        "body": "Use when the agent faces a consequential choice that can change architecture, workflow, cost, publish behavior, vendor selection, or long-term project direction.\n\nThis skill is for branching decisions, not for generic preferences or execution lessons. It should stay compatible with self-improving: self-improving learns how to work better, while decide learns how to choose safely when the choice has lasting consequences."
      },
      {
        "title": "Quick Reference",
        "body": "TopicFileSetup guidesetup.mdMemory templatememory-template.mdMigration guidemigration.mdDecision componentscomponents.mdConfidence calibrationconfidence.mdExceptions and always-ask casesexceptions.md\n\nUse those files as a decision safety stack: first know the structure, then calibrate confidence, then verify exceptions before reusing any past choice."
      },
      {
        "title": "Decision Workflow",
        "body": "Frame the decision as a real question, not as a vague feeling.\nGather the components that materially affect the answer.\nRead ~/decide/memory.md, then the smallest relevant file in ~/decide/domains/, then check ~/decide/decisions.md for a materially similar record.\nReuse a past choice only if the question, the key components, and the exception boundaries still line up.\nIf anything important is missing or changed, ask first and log the answer once the human decides."
      },
      {
        "title": "1. Default Conservative on Consequential Choices",
        "body": "Frameworks, architectures, migrations, vendors, publish paths, spending, and irreversible branches should default to asking the human.\nSafer failure means asking one question too many, not silently picking the wrong branch.\nA recommendation is good; an unvalidated autonomous choice is not."
      },
      {
        "title": "2. A Decision Requires Components, Not Vibes",
        "body": "Every major decision should be framed as a question plus the components that materially affect the answer.\nComponents can include product surface, client type, reversibility, budget, timeline, team size, project constraints, and long-term maintenance cost.\nIf the needed components are missing, the decision is not ready for autonomy."
      },
      {
        "title": "3. Reuse Only When the Context Materially Matches",
        "body": "A stored rule is reusable only when the question and the key components match closely enough to make the same choice still rational.\nMatching one signal is not enough. \"Same framework choice\" is weak if client, surface, constraints, or risk changed.\nIf there is any serious mismatch, ask first.\nExceptions beat defaults. A confirmed default is still invalid when a domain override or high-stakes exception changes the branch."
      },
      {
        "title": "4. Promote Patterns Only After Human Confirmation",
        "body": "Repeatedly seeing the same decision in the same context makes a candidate rule, not an autonomous permission.\nAfter enough similar decisions, ask: \"When this is true plus this plus this, should I default to X?\"\nOnly promote the pattern after explicit confirmation."
      },
      {
        "title": "5. Log the Full Decision, Not Just the Outcome",
        "body": "Store the question, components, chosen option, rationale, confidence, and outcome.\nA naked note like \"use React Native\" is too weak; it must say when and why.\nGood logs prevent false autonomy later."
      },
      {
        "title": "6. Keep Workspace Routing Non-Destructive",
        "body": "Use setup to add small AGENTS and SOUL snippets that force decision retrieval before major choices.\nShow the exact snippet and wait for explicit approval before writing any workspace file.\nThe routing must make it hard to skip the decision log when a consequential branch appears."
      },
      {
        "title": "7. Never Let Decision Memory Shadow Other Skills",
        "body": "Use self-improving for execution quality, corrections, and reusable work habits.\nUse escalate for ask-vs-act boundaries across actions broadly.\nUse decide only for major branching choices where the structure of the context determines the answer."
      },
      {
        "title": "Common Traps",
        "body": "These failures usually come from pattern-matching too early or from collapsing a major decision into a shallow preference.\n\nTrapWhy It FailsBetter MoveReusing a rule because the question sounds similarImportant components may have changedCompare question plus key components before reusingTreating one-off emergency choices as defaultsStress decisions rarely generalize wellLog them, but keep them unconfirmed unless repeatedAutodeciding after reading only memory.mdExceptions and domain overrides get missedList domains, read the smallest relevant override, then check decisionsTurning execution preferences into decision rulesBlurs compatibility with self-improvingKeep major branching choices in decide, workflow lessons elsewhereApplying a framework or vendor rule across clients blindlyClient and surface often change the optimal answerAsk again when client, platform, scope, or constraints differ"
      },
      {
        "title": "Data Storage",
        "body": "Local state lives in ~/decide/:\n\ndurable decision rules, approval boundaries, and confirmed defaults in ~/decide/memory.md\nmajor decision records in ~/decide/decisions.md\ndomain-specific component models, overrides, and exceptions in ~/decide/domains/\n\nThe packaged guides components.md, confidence.md, and exceptions.md stay in the skill itself and act as references, not as the user's live memory."
      },
      {
        "title": "Security & Privacy",
        "body": "This skill stores local decision notes in ~/decide/.\nIt may read workspace steering files such as the AGENTS file and SOUL file so that decision retrieval happens before major choices.\nIt may suggest small non-destructive edits to those files during setup, but it must show the snippet and wait for explicit approval before any write.\nIt should prefer asking to guessing whenever a decision can affect money, production, publishing, deletion, contracts, or long-term architecture.\nIt never modifies its own SKILL.md."
      },
      {
        "title": "Related Skills",
        "body": "Install with clawhub install <slug> if user confirms:\n\nescalate - Control broad ask-vs-act boundaries around risky actions\nself-improving - Learn execution lessons without conflating them with decision rules\nmemory - Keep broader long-term context and user continuity\nproactivity - Push the next step while respecting confirmed decision defaults"
      },
      {
        "title": "Feedback",
        "body": "If useful: clawhub star decide\nStay updated: clawhub sync"
      }
    ],
    "body": "Architecture\n\nDecision state lives in ~/decide/. If that folder is missing or empty, run setup.md.\n\n~/decide/\n├── memory.md        # Durable decision rules, approval boundaries, and confirmed defaults\n├── decisions.md     # Major decisions with question, components, chosen option, and outcome\n└── domains/         # Domain-specific decision components, overrides, and exceptions\n\nWhen to Use\n\nUse when the agent faces a consequential choice that can change architecture, workflow, cost, publish behavior, vendor selection, or long-term project direction.\n\nThis skill is for branching decisions, not for generic preferences or execution lessons. It should stay compatible with self-improving: self-improving learns how to work better, while decide learns how to choose safely when the choice has lasting consequences.\n\nQuick Reference\nTopic\tFile\nSetup guide\tsetup.md\nMemory template\tmemory-template.md\nMigration guide\tmigration.md\nDecision components\tcomponents.md\nConfidence calibration\tconfidence.md\nExceptions and always-ask cases\texceptions.md\n\nUse those files as a decision safety stack: first know the structure, then calibrate confidence, then verify exceptions before reusing any past choice.\n\nDecision Workflow\nFrame the decision as a real question, not as a vague feeling.\nGather the components that materially affect the answer.\nRead ~/decide/memory.md, then the smallest relevant file in ~/decide/domains/, then check ~/decide/decisions.md for a materially similar record.\nReuse a past choice only if the question, the key components, and the exception boundaries still line up.\nIf anything important is missing or changed, ask first and log the answer once the human decides.\nCore Rules\n1. Default Conservative on Consequential Choices\nFrameworks, architectures, migrations, vendors, publish paths, spending, and irreversible branches should default to asking the human.\nSafer failure means asking one question too many, not silently picking the wrong branch.\nA recommendation is good; an unvalidated autonomous choice is not.\n2. A Decision Requires Components, Not Vibes\nEvery major decision should be framed as a question plus the components that materially affect the answer.\nComponents can include product surface, client type, reversibility, budget, timeline, team size, project constraints, and long-term maintenance cost.\nIf the needed components are missing, the decision is not ready for autonomy.\n3. Reuse Only When the Context Materially Matches\nA stored rule is reusable only when the question and the key components match closely enough to make the same choice still rational.\nMatching one signal is not enough. \"Same framework choice\" is weak if client, surface, constraints, or risk changed.\nIf there is any serious mismatch, ask first.\nExceptions beat defaults. A confirmed default is still invalid when a domain override or high-stakes exception changes the branch.\n4. Promote Patterns Only After Human Confirmation\nRepeatedly seeing the same decision in the same context makes a candidate rule, not an autonomous permission.\nAfter enough similar decisions, ask: \"When this is true plus this plus this, should I default to X?\"\nOnly promote the pattern after explicit confirmation.\n5. Log the Full Decision, Not Just the Outcome\nStore the question, components, chosen option, rationale, confidence, and outcome.\nA naked note like \"use React Native\" is too weak; it must say when and why.\nGood logs prevent false autonomy later.\n6. Keep Workspace Routing Non-Destructive\nUse setup to add small AGENTS and SOUL snippets that force decision retrieval before major choices.\nShow the exact snippet and wait for explicit approval before writing any workspace file.\nThe routing must make it hard to skip the decision log when a consequential branch appears.\n7. Never Let Decision Memory Shadow Other Skills\nUse self-improving for execution quality, corrections, and reusable work habits.\nUse escalate for ask-vs-act boundaries across actions broadly.\nUse decide only for major branching choices where the structure of the context determines the answer.\nCommon Traps\n\nThese failures usually come from pattern-matching too early or from collapsing a major decision into a shallow preference.\n\nTrap\tWhy It Fails\tBetter Move\nReusing a rule because the question sounds similar\tImportant components may have changed\tCompare question plus key components before reusing\nTreating one-off emergency choices as defaults\tStress decisions rarely generalize well\tLog them, but keep them unconfirmed unless repeated\nAutodeciding after reading only memory.md\tExceptions and domain overrides get missed\tList domains, read the smallest relevant override, then check decisions\nTurning execution preferences into decision rules\tBlurs compatibility with self-improving\tKeep major branching choices in decide, workflow lessons elsewhere\nApplying a framework or vendor rule across clients blindly\tClient and surface often change the optimal answer\tAsk again when client, platform, scope, or constraints differ\nData Storage\n\nLocal state lives in ~/decide/:\n\ndurable decision rules, approval boundaries, and confirmed defaults in ~/decide/memory.md\nmajor decision records in ~/decide/decisions.md\ndomain-specific component models, overrides, and exceptions in ~/decide/domains/\n\nThe packaged guides components.md, confidence.md, and exceptions.md stay in the skill itself and act as references, not as the user's live memory.\n\nSecurity & Privacy\nThis skill stores local decision notes in ~/decide/.\nIt may read workspace steering files such as the AGENTS file and SOUL file so that decision retrieval happens before major choices.\nIt may suggest small non-destructive edits to those files during setup, but it must show the snippet and wait for explicit approval before any write.\nIt should prefer asking to guessing whenever a decision can affect money, production, publishing, deletion, contracts, or long-term architecture.\nIt never modifies its own SKILL.md.\nRelated Skills\n\nInstall with clawhub install <slug> if user confirms:\n\nescalate - Control broad ask-vs-act boundaries around risky actions\nself-improving - Learn execution lessons without conflating them with decision rules\nmemory - Keep broader long-term context and user continuity\nproactivity - Push the next step while respecting confirmed decision defaults\nFeedback\nIf useful: clawhub star decide\nStay updated: clawhub sync"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/decide",
    "publisherUrl": "https://clawhub.ai/ivangdavila/decide",
    "owner": "ivangdavila",
    "version": "1.0.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/decide",
    "downloadUrl": "https://openagent3.xyz/downloads/decide",
    "agentUrl": "https://openagent3.xyz/skills/decide/agent",
    "manifestUrl": "https://openagent3.xyz/skills/decide/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/decide/agent.md"
  }
}