[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78GPRNJ0P23PDMYV8SDFDXC":3,"skill-same:01M78GPRNJ0P23PDMYV8SDFDXC":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78GPRNJ0P23PDMYV8SDFDXC","poke-holes",null,"Trigger immediately when the user says any of: 'poke holes', 'grill me', 'grill me on this', 'stress test', 'stress-test this', 'challenge this', 'push back on this', 'interrogate me', 'interview me about this'. Then interview the user relentlessly about an existing plan, spec, or design until reaching shared understanding, resolving each branch of the decision tree. Do not skip this skill and answer the user's questions conversationally yourself — even one trigger phrase fires it, and auto mode does not bypass it.","sandsower\u002Fnopal","sandsower","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F302322?v=4","01M78GNBK4G12AGP2PA2FND7R4","Vic Valenzuela","01M78GNBM80RBPX57WYVHFHC97",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fpoke-holes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: poke-holes\ndescription: \"Trigger immediately when the user says any of: 'poke holes', 'grill me', 'grill me on this', 'stress test', 'stress-test this', 'challenge this', 'push back on this', 'interrogate me', 'interview me about this'. Then interview the user relentlessly about an existing plan, spec, or design until reaching shared understanding, resolving each branch of the decision tree. Do not skip this skill and answer the user's questions conversationally yourself — even one trigger phrase fires it, and auto mode does not bypass it.\"\n---\n\nRequires an existing plan, spec, or design to pressure-test. Not for extracting requirements from scratch — use `spec` for that.\n\nOptional visual routing: only when repo-level `beislid:visual_surfaces` config exists and the effective `poke-holes` mode is active, load `visual-surface-protocol.md`; it mirrors canonical `.beislid\u002Fvisual-surface-protocol.md` for copied installs. Use Lavish conservatively, only when a decision tree, branching tradeoff matrix, risk map, architecture\u002Fdependency diagram, or visual input control materially improves the stress test. Absent config or `off` must not mention or invoke Lavish.\n\n## Workflow signals\n\nWhen `workflow_signals` is configured, use the best-effort CLI to expose semantic state:\n\n- At start\u002Fresume of interrogation, emit `beislid workflow-signal emit working --skill poke-holes --phase interrogate`.\n- If no existing plan\u002Fspec\u002Fdesign is available, emit `beislid workflow-signal emit blocked --skill poke-holes --phase missing-input` before asking the user to provide one or route to `spec`.\n- Before every interview question that needs the user's answer, emit `beislid workflow-signal emit waiting --skill poke-holes --phase question`.\n- When exploring the codebase to answer a question from evidence, emit `beislid workflow-signal emit working --skill poke-holes --phase explore`.\n- When shared understanding is reached and the stress-test is complete, emit `beislid workflow-signal emit done --skill poke-holes --phase complete`.\n\nThe command is safe to call even when unconfigured, outside tmux, or without `tmux-glance`; it no-ops rather than blocking the interview.\n\nInterview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.\n\nIf a question can be answered by exploring the codebase, explore the codebase instead.\n\nWhen active visual routing is useful, apply the protocol at a concrete branch\u002Fdecision\u002Frevision boundary, not for every interview turn. Respect `suggest`\u002F`prompt`\u002F`auto` exactly; unattended `prompt` mode falls back to Markdown\u002Fchat unless the run envelope already grants permission. The supplemental surface should use `comparison`, `diagram`, and `input` playbook guidance and include one typed `BEISLID_VISUAL_FEEDBACK_V1` gate for `workflow: poke-holes`, action `resolve_revise_or_choose_poke_holes`, and decisions `resolved`, `revise`, or `choose` (`choose` requires `selected_option`). Copy accepted visual resolutions, revisions, or branch choices into the canonical Markdown\u002Fchat stress-test record before marking the check complete or routing back to the owning planning skill; visual controls never approve implementation by themselves.\n","Requires an existing plan, spec, or design to pressure-test. Not for extracting requirements from scratch — use `spec` for that.\n\nOptional visual routing: only when repo-level `beislid:visual_surfaces` config exists and the effective `poke-holes` mode is active, load `visual-surface-protocol.md`; it mirrors canonical `.beislid\u002Fvisual-surface-protocol.md` for copied installs. Use Lavish conservatively, only when a decision tree, branching tradeoff matrix, risk map, architecture\u002Fdependency diagram, or visual input control materially improves the stress test. Absent config or `off` must not mention or invoke Lavish.\n\n## Workflow signals\n\nWhen `workflow_signals` is configured, use the best-effort CLI to expose semantic state:\n\n- At start\u002Fresume of interrogation, emit `beislid workflow-signal emit working --skill poke-holes --phase interrogate`.\n- If no existing plan\u002Fspec\u002Fdesign is available, emit `beislid workflow-signal emit blocked --skill poke-holes --phase missing-input` before asking the user to provide one or route to `spec`.\n- Before every interview question that needs the user's answer, emit `beislid workflow-signal emit waiting --skill poke-holes --phase question`.\n- When exploring the codebase to answer a question from evidence, emit `beislid workflow-signal emit working --skill poke-holes --phase explore`.\n- When shared understanding is reached and the stress-test is complete, emit `beislid workflow-signal emit done --skill poke-holes --phase complete`.\n\nThe command is safe to call even when unconfigured, outside tmux, or without `tmux-glance`; it no-ops rather than blocking the interview.\n\nInterview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.\n\nIf a question can be answered by exploring the codebase, explore the codebase instead.\n\nWhen active visual routing is useful, apply the protocol at a concrete branch\u002Fdecision\u002Frevision boundary, not for every interview turn. Respect `suggest`\u002F`prompt`\u002F`auto` exactly; unattended `prompt` mode falls back to Markdown\u002Fchat unless the run envelope already grants permission. The supplemental surface should use `comparison`, `diagram`, and `input` playbook guidance and include one typed `BEISLID_VISUAL_FEEDBACK_V1` gate for `workflow: poke-holes`, action `resolve_revise_or_choose_poke_holes`, and decisions `resolved`, `revise`, or `choose` (`choose` requires `selected_option`). Copy accepted visual resolutions, revisions, or branch choices into the canonical Markdown\u002Fchat stress-test record before marking the check complete or routing back to the owning planning skill; visual controls never approve implementation by themselves.\n",{"name":5,"description":7},"main","bba9b487e6731261bcfe35e17ea03269cf8df0a1","resources\u002Fbeislid\u002Fskills\u002Fpoke-holes","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal","https:\u002F\u002Fnopal.sh","https:\u002F\u002Fgithub.com\u002Fsandsower","vic.valenzuela.is","Product-minded software engineer","2026-10-15 00:33:24",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add sandsower\u002Fnopal --skill poke-holes",{"tool":39,"command":40},"bunx","bunx skills add sandsower\u002Fnopal --skill poke-holes",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sandsower\u002Fnopal --skill poke-holes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fpoke-holes\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"visual-surface-protocol.md","REFERENCE","参考文档",26191,"https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fpoke-holes\u002Fvisual-surface-protocol.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M78GRB8RYKHHGYZF3FGN9Y5P","walk-the-diff","Use when the user wants to walk through their local changes interactively before or instead of a PR review — e.g., \"guided review\", \"walk me through the changes\", \"review my branch\", \"let's go through the diff\". Also use when the user explicitly invokes the walk-the-diff skill through the host agent. This is for interactive human-facing walkthroughs of code changes, not automated code review.","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fwalk-the-diff\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78GR8YWH8JMB2E9RRSAR7SF","verify","Use before claiming work is complete, fixed, or passing. Requires running verification commands and reading output before making any success claims. Evidence before assertions.","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78GR26XMDX0KAF5MYZ2W0TN","spec","Trigger immediately when the user says any of: 'spec it out', 'spec this out', 'before you build', 'before we build', 'before implementation', 'let's discuss before building', 'discuss and spec', 'PRD this', 'shape this', 'product spec', 'lightweight spec'. Also use for brainstorming, vague tickets, product shaping, or writing a lightweight product spec\u002FPRD when the problem, scope, desired behavior, or success criteria are unclear. Do not skip this skill and answer conversationally yourself — if a trigger phrase appears, route here even if the request seems clear or auto mode is active. Do not use for implementation design when requirements are already clear; use blueprint instead.","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78GQXP7EJ8WHHZJ4H1NNN0N","show-me","Use when the user asks for a visual HTML evidence\u002Fexplanation artifact: 'show-me', 'show me this', 'make a proof deck', 'make an HTML deck', 'visualize this as HTML', 'this would be better as slides', 'make this visual', 'create a walkthrough deck', 'document this visually', or 'review this visually'. Manual\u002Fuser-requested only in v1. Produces a polished local HTML portfolio\u002Fdeck with evidence, media, logs, provenance, and clear missing-evidence markers.","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fshow-me\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78GQS6VPCC70BNE86HSAF6S","setup","Configure Beislið project config (`.beislid\u002Fworkflow.md`) interactively, or update an installed Beislið distribution. Use when the user says \"setup\", \"\u002Fsetup\", \"setup update\", \"\u002Fsetup update\", \"update beislid\", \"configure beislid\", \"set up workflow\", \"add scopes\", \"change ticket source\", \"reconfigure beislid\", or any intent to add, change, or remove a workflow.md section. Walks through sections conversationally; shows a diff before any destructive write.","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M78GQNPYS736XNYDGKW5N7F4","rinse","Use when the user asks to 'rinse', 'run a review\u002Ffix loop', 'iterate on review findings', 'review and fix until clean', or harden a branch before PR handoff. Orchestrates side-effect-free review, user-approved fixes, verification, reruns, and redesign stop conditions.","https:\u002F\u002Fgithub.com\u002Fsandsower\u002Fnopal\u002Fblob\u002Fmain\u002Fresources\u002Fbeislid\u002Fskills\u002Frinse\u002FSKILL.md",[],[]]