[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79A32ASAS8K1Z19V5CQC425":3,"skill-same:01M79A32ASAS8K1Z19V5CQC425":63},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M79A32ASAS8K1Z19V5CQC425","vault-unseal",null,"Prepare a scoped, time-bounded vault-unseal request for approval and adapter execution; never returns a secret or claims a handle was issued.","ZachDreamZ\u002Frunx","ZachDreamZ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22769595?v=4","01M799NTP9N5VYWB4JY50MC7Y3","NexusCore","01M799NTQ1AYT8TZC0XTSEZXDJ",0,"MIT","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvault-unseal\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vault-unseal\ndescription: Prepare a scoped, time-bounded vault-unseal request for approval and adapter execution; never returns a secret or claims a handle was issued.\nrunx:\n  category: security\n---\n\n# Vault Unseal\n\nTurn a request for a secret into a reviewable, time-bounded access plan that\nhands an approval-ready request to a vault adapter instead of exposing the secret.\n\n## What this skill does\n\nAn agent rarely needs a secret. It needs the thing the secret unlocks: one API\ncall, one signed request, one decrypt for a stated window. This skill plans that\naccess. It binds the secret reference, the purpose, a TTL, the scope the secret\ncovers, and the principal asking, then marks the request for a human approval\ngate. The output is an unseal plan; it does not contain a handle or an\naudit receipt because this agent runner cannot issue either. A configured vault\nadapter performs the live unseal after approval and owns its handle and audit\nevidence. The secret value is never read into the plan, the receipt, or the\nagent's context.\n\nIt governs explicit secret access with a TTL and approval; least-privilege\nonly analyzes scopes, it never touches secrets.\n\n## When to use this skill\n\n- An agent or workflow needs a credential, key, or token to complete one bounded\n  task and the access must be approved and audited.\n- A break-glass or just-in-time access request needs a plan a reviewer can read\n  and a window that expires on its own.\n- A downstream action skill needs an approval-ready request that a vault adapter\n  can exchange for a handle without putting the secret in agent context.\n- An operator wants the planning decision (`ready_for_approval`, `needs_agent`,\n  `denied`) separated from adapter-owned execution evidence.\n\n## When not to use this skill\n\n- To read, print, copy, or return a secret value or handle. This skill prepares\n  the request; the vault adapter owns live access.\n- To grant standing or unbounded access. Every unseal is scoped to one secret\n  for one TTL.\n- To review or narrow scopes that a subject already holds. Use\n  least-privilege for scope analysis against receipts.\n- To rotate, store, or mint new secrets. That is a separate vault operation with\n  its own gate.\n- To bypass the approval gate, widen the scope past the stated purpose, or\n  extend a TTL that has already lapsed.\n\n## Procedure\n\n1. Resolve the request. Confirm `secret_ref`, `purpose`, `ttl`, `scope`, and\n   `principal` are present. If any required input is missing, stop with\n   `needs_agent` and name what is missing. Do not guess a default TTL or scope.\n2. Check purpose and scope against policy. Confirm the stated purpose is a\n   permitted reason to access this secret, and that the scope does not exceed\n   what the purpose needs. If the purpose or scope is not permitted, set\n   `decision: denied` and name the policy that refused, not the secret.\n3. Set the TTL window. Parse `ttl` into a duration; the window starts at\n   approval, not at request. If the TTL is unparseable, absent, or unbounded,\n   return `needs_agent`. There is no open-ended unseal.\n4. Set the approval gate. A live unseal always requires human approval; set\n   `gates.human_approval_required: true`. A complete, permitted request is\n   `ready_for_approval`, never evidence that approval or execution occurred.\n5. Bind the request. Bind the plan to exactly one `secret_ref` for one TTL\n   window under the requested scope. Set `decision: ready_for_approval` only\n   when the request is complete and policy-compatible.\n6. Hand off execution. After separate approval evidence is attached, a vault\n   adapter may consume the plan, issue an opaque handle, and return adapter-owned\n   audit evidence. This skill never fabricates either outcome.\n\n## Edge cases and stop conditions\n\n- **Missing required input:** `secret_ref`, `purpose`, `ttl`, or `scope` absent\n  returns `needs_agent`. The principal is also required to attribute the access.\n- **Purpose not permitted:** set `decision: denied`; name the refusing policy,\n  never the secret.\n- **Scope exceeds purpose:** narrow to what the purpose needs, or set\n  `decision: denied` if it cannot be narrowed safely.\n- **Unbounded or lapsed TTL:** refuse. There is no standing unseal and no revival\n  of an expired window.\n- **Approval absent or denied:** the request remains `ready_for_approval` or\n  moves to `denied`; this skill never issues a handle.\n- **Caller asks for the raw value:** refuse that part. If the workflow genuinely\n  cannot use an adapter-owned handle, return `needs_agent` with the constraint\n  named, never the value.\n- **Vault adapter unavailable:** return an execution blocker; a plan is not an\n  unseal.\n\n## Output schema\n\nThe artifact is the `unseal_plan` object, wrapped as `runx.unseal.v1`. The\nsecret value never appears in any field.\n\n```yaml\nunseal_plan:\n  decision: ready_for_approval | needs_agent | denied\n  secret_ref: string        # reference to the secret, never its value\n  purpose: string           # bounded reason the secret is needed\n  ttl: string               # bound duration; the window starts at approval\n  scope:                    # what the secret unlocks, as stated and as bound\n    resource: string\n    action: string\n    path: string\n  principal: string         # who the access is attributed to\n  gates:\n    human_approval_required: boolean  # always true for a live unseal\n  blockers: array           # named reasons the plan is not ready\n  execution:\n    requires_adapter: true\n    requires_approval: true\n```\n\n## Worked example\n\nInput: principal `svc\u002Freport-exporter` requests `vault:\u002F\u002Fdrive\u002Fservice-account`\nfor the purpose \"sign one Drive export request\", `ttl: 10m`, scope\n`{ resource: drive.files, action: export, path: \u002Freports\u002F* }`.\n\nOutput: `decision: ready_for_approval`; policy permits the purpose and the scope\nmatches it; `gates.human_approval_required: true`; and\n`execution.requires_adapter: true`. After explicit approval, the vault adapter\nmay issue an opaque handle and records its own audit evidence. The service\naccount key never enters the plan or the receipt.\n\n## Inputs\n\n- `secret_ref` (required): reference to the secret to unseal, never its value.\n- `purpose` (required): the bounded reason the secret is needed.\n- `ttl` (required): the access window duration; the window starts at approval.\n- `scope` (required): structured statement of what the secret unlocks.\n- `principal` (required): who the access is attributed to.\n- `policy_notes` (optional): reserved purposes, break-glass conditions, or\n  constraints that affect the decision.\n- `operator_context` (optional): approval posture or extra guardrails.\n","# Vault Unseal\n\nTurn a request for a secret into a reviewable, time-bounded access plan that\nhands an approval-ready request to a vault adapter instead of exposing the secret.\n\n## What this skill does\n\nAn agent rarely needs a secret. It needs the thing the secret unlocks: one API\ncall, one signed request, one decrypt for a stated window. This skill plans that\naccess. It binds the secret reference, the purpose, a TTL, the scope the secret\ncovers, and the principal asking, then marks the request for a human approval\ngate. The output is an unseal plan; it does not contain a handle or an\naudit receipt because this agent runner cannot issue either. A configured vault\nadapter performs the live unseal after approval and owns its handle and audit\nevidence. The secret value is never read into the plan, the receipt, or the\nagent's context.\n\nIt governs explicit secret access with a TTL and approval; least-privilege\nonly analyzes scopes, it never touches secrets.\n\n## When to use this skill\n\n- An agent or workflow needs a credential, key, or token to complete one bounded\n  task and the access must be approved and audited.\n- A break-glass or just-in-time access request needs a plan a reviewer can read\n  and a window that expires on its own.\n- A downstream action skill needs an approval-ready request that a vault adapter\n  can exchange for a handle without putting the secret in agent context.\n- An operator wants the planning decision (`ready_for_approval`, `needs_agent`,\n  `denied`) separated from adapter-owned execution evidence.\n\n## When not to use this skill\n\n- To read, print, copy, or return a secret value or handle. This skill prepares\n  the request; the vault adapter owns live access.\n- To grant standing or unbounded access. Every unseal is scoped to one secret\n  for one TTL.\n- To review or narrow scopes that a subject already holds. Use\n  least-privilege for scope analysis against receipts.\n- To rotate, store, or mint new secrets. That is a separate vault operation with\n  its own gate.\n- To bypass the approval gate, widen the scope past the stated purpose, or\n  extend a TTL that has already lapsed.\n\n## Procedure\n\n1. Resolve the request. Confirm `secret_ref`, `purpose`, `ttl`, `scope`, and\n   `principal` are present. If any required input is missing, stop with\n   `needs_agent` and name what is missing. Do not guess a default TTL or scope.\n2. Check purpose and scope against policy. Confirm the stated purpose is a\n   permitted reason to access this secret, and that the scope does not exceed\n   what the purpose needs. If the purpose or scope is not permitted, set\n   `decision: denied` and name the policy that refused, not the secret.\n3. Set the TTL window. Parse `ttl` into a duration; the window starts at\n   approval, not at request. If the TTL is unparseable, absent, or unbounded,\n   return `needs_agent`. There is no open-ended unseal.\n4. Set the approval gate. A live unseal always requires human approval; set\n   `gates.human_approval_required: true`. A complete, permitted request is\n   `ready_for_approval`, never evidence that approval or execution occurred.\n5. Bind the request. Bind the plan to exactly one `secret_ref` for one TTL\n   window under the requested scope. Set `decision: ready_for_approval` only\n   when the request is complete and policy-compatible.\n6. Hand off execution. After separate approval evidence is attached, a vault\n   adapter may consume the plan, issue an opaque handle, and return adapter-owned\n   audit evidence. This skill never fabricates either outcome.\n\n## Edge cases and stop conditions\n\n- **Missing required input:** `secret_ref`, `purpose`, `ttl`, or `scope` absent\n  returns `needs_agent`. The principal is also required to attribute the access.\n- **Purpose not permitted:** set `decision: denied`; name the refusing policy,\n  never the secret.\n- **Scope exceeds purpose:** narrow to what the purpose needs, or set\n  `decision: denied` if it cannot be narrowed safely.\n- **Unbounded or lapsed TTL:** refuse. There is no standing unseal and no revival\n  of an expired window.\n- **Approval absent or denied:** the request remains `ready_for_approval` or\n  moves to `denied`; this skill never issues a handle.\n- **Caller asks for the raw value:** refuse that part. If the workflow genuinely\n  cannot use an adapter-owned handle, return `needs_agent` with the constraint\n  named, never the value.\n- **Vault adapter unavailable:** return an execution blocker; a plan is not an\n  unseal.\n\n## Output schema\n\nThe artifact is the `unseal_plan` object, wrapped as `runx.unseal.v1`. The\nsecret value never appears in any field.\n\n```yaml\nunseal_plan:\n  decision: ready_for_approval | needs_agent | denied\n  secret_ref: string        # reference to the secret, never its value\n  purpose: string           # bounded reason the secret is needed\n  ttl: string               # bound duration; the window starts at approval\n  scope:                    # what the secret unlocks, as stated and as bound\n    resource: string\n    action: string\n    path: string\n  principal: string         # who the access is attributed to\n  gates:\n    human_approval_required: boolean  # always true for a live unseal\n  blockers: array           # named reasons the plan is not ready\n  execution:\n    requires_adapter: true\n    requires_approval: true\n```\n\n## Worked example\n\nInput: principal `svc\u002Freport-exporter` requests `vault:\u002F\u002Fdrive\u002Fservice-account`\nfor the purpose \"sign one Drive export request\", `ttl: 10m`, scope\n`{ resource: drive.files, action: export, path: \u002Freports\u002F* }`.\n\nOutput: `decision: ready_for_approval`; policy permits the purpose and the scope\nmatches it; `gates.human_approval_required: true`; and\n`execution.requires_adapter: true`. After explicit approval, the vault adapter\nmay issue an opaque handle and records its own audit evidence. The service\naccount key never enters the plan or the receipt.\n\n## Inputs\n\n- `secret_ref` (required): reference to the secret to unseal, never its value.\n- `purpose` (required): the bounded reason the secret is needed.\n- `ttl` (required): the access window duration; the window starts at approval.\n- `scope` (required): structured statement of what the secret unlocks.\n- `principal` (required): who the access is attributed to.\n- `policy_notes` (optional): reserved purposes, break-glass conditions, or\n  constraints that affect the decision.\n- `operator_context` (optional): approval posture or extra guardrails.\n",{"name":5,"runx":24,"description":7},{"category":25},"security","main","fe90232960df6d9653e72e8d024a9d859e1ae524","skills\u002Fvault-unseal","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx","https:\u002F\u002Frunx.ai","https:\u002F\u002Fgithub.com\u002FZachDreamZ","https:\u002F\u002Fagentapigw.dpdns.org","Building Agent API Gateway — structured web data for AI agents. Consistent until I make it.","2026-07-17 04:21:10",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ZachDreamZ\u002Frunx --skill vault-unseal",{"tool":41,"command":42},"bunx","bunx skills add ZachDreamZ\u002Frunx --skill vault-unseal",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ZachDreamZ\u002Frunx --skill vault-unseal","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvault-unseal\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"fixtures\u002Funseal-missing-inputs.yaml","REFERENCE","参考文档",759,"https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvault-unseal\u002Ffixtures\u002Funseal-missing-inputs.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"fixtures\u002Funseal-plan-approved.yaml",1028,"https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvault-unseal\u002Ffixtures\u002Funseal-plan-approved.yaml",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"X.yaml",1408,"https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvault-unseal\u002FX.yaml",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79A3PCWPN0YG6XG3X2YWGY4","zapier-handoff","Validate a runx execution context and hand off a governed payload to a Zapier Catch Hook with scoped auth, idempotency, and receipt expectations.","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-handoff\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79A3JPAJVDGX5AGXKHB6M58","x402-pay","Execute a governed x402 payment by delegating to the canonical spend flow with the x402 runtime path selected.","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fx402-pay\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79A3H7HHAQ5B4QCA0S2PPA3","work-plan","Decompose a build objective into governed runx execution steps.","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fwork-plan\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79A3ESQDZ6AQ3QASKYGYTNB","web-fetch","Fetch and extract one web source within an explicit allowlist, returning the content by digest with full provenance.","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fweb-fetch\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79A3C9NE99P24Q2QGG5236D","weather-forecast","Normalize provider weather evidence into an action-safe forecast packet with provenance, uncertainty, and stop conditions for downstream agents.","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fweather-forecast\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79A38RWEA5NHMYBQZPCVPQP","vuln-triage","Triage dependency or ecosystem vulnerability risk into remediation and advisory packets, grounding on verified CVE evidence when it is supplied.","https:\u002F\u002Fgithub.com\u002FZachDreamZ\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-triage\u002FSKILL.md",[],[]]