[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BK79K4SZ1V2PWAHD8VHTME":3,"skill-same:01M7BK79K4SZ1V2PWAHD8VHTME":69},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BK79K4SZ1V2PWAHD8VHTME","setup-agy-skills",null,"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","fderuiter\u002Fagy-skills","fderuiter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127706008?v=4","01M6C40AWP9EPQBS3EG0RF5DRD","Frederick de Ruiter","01M7BK63K60DTR50H82SAHMYHK",1,"MIT","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: setup-agy-skills\ndescription: \"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.\"\n---\n\n# Setup AGY Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker**: where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig`: is this a GitHub repo? Which one?\n- `AGENTS.md`, `GEMINI.md`, or `CLAUDE.md` at the repo root: does one exist? Is there already an `## Agent skills` section in it?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F`: does this skill's prior output already exist?\n- `.scratch\u002F`: a sign that a local-markdown issue tracker convention is already in use\n- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.\n- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order using the `ask_question` tool (with chat fallback if absent). One section, one interactive choice, then the next.\n\nPresent options via `ask_question` with the recommended answer marked `(Recommended)`. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).\n\n**Section A: Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub**: issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab**: issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown**: issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\nRecord the choice in `docs\u002Fagents\u002Fissue-tracker.md`. The GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.\n\n**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C: Domain docs.** Default to **single-context** (one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root). This fits almost every repo; write it without asking.\n\nOffer **multi-context** (a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files) only when exploration found monorepo signals. Then confirm which layout they want.\n\n**Section D: Antigravity Lifecycle Hooks.** Ask whether the user wants to enable recommended safety guardrails in `.agents\u002Fhooks.json` (recommended: **yes**):\n\n> Would you like to enable Antigravity lifecycle hooks (such as blocking destructive git commands like `git push` or `git reset --hard`, and enforcing prose formatting invariants)? (recommended: **yes**)\n\nOn **yes**, scaffold `.agents\u002Fhooks.json`, `.agents\u002Fhooks\u002Fblock-dangerous-git.js`, and `.agents\u002Fhooks\u002Fcheck-prose-invariants.js`.\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever rule file (`AGENTS.md`, `GEMINI.md`, or `CLAUDE.md`) is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\n- The `.agents\u002Fhooks.json` configuration (if Section D was accepted)\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `AGENTS.md` exists, edit it.\n- Else if `GEMINI.md` exists, edit it.\n- Else if `CLAUDE.md` exists, edit it.\n- If none exists, create `AGENTS.md`.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout: \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\n\nThen write the docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md): GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md): GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md): local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n","# Setup AGY Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker**: where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig`: is this a GitHub repo? Which one?\n- `AGENTS.md`, `GEMINI.md`, or `CLAUDE.md` at the repo root: does one exist? Is there already an `## Agent skills` section in it?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F`: does this skill's prior output already exist?\n- `.scratch\u002F`: a sign that a local-markdown issue tracker convention is already in use\n- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.\n- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order using the `ask_question` tool (with chat fallback if absent). One section, one interactive choice, then the next.\n\nPresent options via `ask_question` with the recommended answer marked `(Recommended)`. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).\n\n**Section A: Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub**: issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab**: issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown**: issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\nRecord the choice in `docs\u002Fagents\u002Fissue-tracker.md`. The GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.\n\n**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C: Domain docs.** Default to **single-context** (one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root). This fits almost every repo; write it without asking.\n\nOffer **multi-context** (a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files) only when exploration found monorepo signals. Then confirm which layout they want.\n\n**Section D: Antigravity Lifecycle Hooks.** Ask whether the user wants to enable recommended safety guardrails in `.agents\u002Fhooks.json` (recommended: **yes**):\n\n> Would you like to enable Antigravity lifecycle hooks (such as blocking destructive git commands like `git push` or `git reset --hard`, and enforcing prose formatting invariants)? (recommended: **yes**)\n\nOn **yes**, scaffold `.agents\u002Fhooks.json`, `.agents\u002Fhooks\u002Fblock-dangerous-git.js`, and `.agents\u002Fhooks\u002Fcheck-prose-invariants.js`.\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever rule file (`AGENTS.md`, `GEMINI.md`, or `CLAUDE.md`) is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\n- The `.agents\u002Fhooks.json` configuration (if Section D was accepted)\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `AGENTS.md` exists, edit it.\n- Else if `GEMINI.md` exists, edit it.\n- Else if `CLAUDE.md` exists, edit it.\n- If none exists, create `AGENTS.md`.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout: \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\n\nThen write the docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md): GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md): GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md): local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n",{"name":5,"description":7},"main","97b7a56459bd17362bf4f075d60d92c1ae6cce33","skills\u002Fengineering\u002Fsetup-agy-skills",0,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills","https:\u002F\u002Ffderuiter.github.io\u002Fagy-skills\u002F","https:\u002F\u002Fgithub.com\u002Ffderuiter","Clinical Data Specialist at @Bright-Research \r\n\r\nInterests in Photogrammetry, Data Analytics + Pipelines, Mathematics, and AI\u002FML.\r\n\r\nPython, Rust, TS.","2026-08-29 02:26:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add fderuiter\u002Fagy-skills --skill setup-agy-skills",{"tool":39,"command":40},"bunx","bunx skills add fderuiter\u002Fagy-skills --skill setup-agy-skills",{"tool":42,"command":43},"pnpm","pnpm dlx skills add fderuiter\u002Fagy-skills --skill setup-agy-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002FSKILL.md",true,[47,53,57,61,65],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"domain.md","REFERENCE","参考文档",2033,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002Fdomain.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"issue-tracker-github.md",3731,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002Fissue-tracker-github.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"issue-tracker-gitlab.md",3809,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002Fissue-tracker-gitlab.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"issue-tracker-local.md",1810,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002Fissue-tracker-local.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fsetup-agy-skills\u002Ftriage-labels.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7BK91P025C72NSC9NZTS4JF","writing-shape","Shape raw material into an article paragraph by paragraph, arguing format choices along the way.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7BK908F7QPQST3FKHAAVE87","writing-fragments","Mine raw writing fragments with no structure yet, capturing ideas into a single quarry file.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7BK8YJEBD31HR3GTYATQ6ZA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7BK8WWERTYDTVVE95VMKZ2J","writing-beats","Assemble raw material into a narrative journey of beats, grounding concepts before leaning on them.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-beats\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7BK8VT41ZSQVB6TFM2KZRBZ","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7BK8T2V1J99DXH22Q304T4S","to-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002Ffderuiter\u002Fagy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fto-questionnaire\u002FSKILL.md",[],[]]