[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FQHSMA1MSSD1F4NKJP248":3,"skill-same:01M74FQHSMA1MSSD1F4NKJP248":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M74FQHSMA1MSSD1F4NKJP248","get-connected",null,"Chat and Claude Code: Step 0 of the discover journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly.","Eliyce\u002Fpaqad-ai","Eliyce","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F173689792?v=4","01M74F7NHRXY2FW9KM93WHKHST","01M74F7NJDEWZ2XM9CQV70T3JK",8,"MIT","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: get-connected\ndescription: \"Chat and Claude Code: Step 0 of the discover journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly.\"\ncompatibility: \"claude.ai chat, Cowork or Claude Code; reads project docs and code through a connector, uploaded files or the open folder\"\n---\n\n# get-connected\n\nHow to talk: follow `references\u002Fvoice.md`. Short, answer first, plain business words, no narration,\none short sources line. Those rules win.\n\nStep 0: get connected. Fills the `setup` block.\n\n## When this runs\n\nDirected by the discover journey; not started directly.\n\n## What it does\n\nWork out which sources can be read, the repository first and the tracker second, and record them in\norder in `setup.grounding_sources` (`references\u002Fground-from-tracker.md`).\n\n1. Choose and reach the repository by capability (`references\u002Fconnect-repository.md`), then detect\n   its evidence level (`references\u002Fevidence-levels.md`) with `scripts\u002Fcheck_onboarded.py`. project-docs (ready): carry on from project docs.\n   docs-and-code (partly ready): carry on, say its message once and name the areas without a summary\n   as not documented. code-only (not set up, with reachable code): carry on from code by names, as\n   what the code suggests. Stop only when nothing is readable. Store the choice in `setup.repository`, its state in `setup.repository_state`,\n   and the level in `setup.evidence_level`. When a repository connector is switched on but offers no\n   list or read action, say this once and carry on tracker only, with `setup.repository_state`\n   `connector-unreadable`:\n   \"GitHub is connected, but I can't read any repositories through it from here. I'll work from the tickets for now. To use the code and docs, attach the repository or its docs folder.\"\n   A read that fails on sign-in or a rate limit is not this case and never gets that sentence. With\n   no readable tracker either, say nothing can be read, as in step 3, and stop.\n2. Find the Jira project from the repository, before any tracker read. With no readable repository\n   skip this and ask which project to use. With the repository connector's list actions, resolved by\n   capability, read up to 100 branch names and the subjects of the last 50 commits on the default\n   branch, newest first, and pipe them one per line to `scripts\u002Ffind_ticket_keys.py`. Store only its\n   counts in `setup.ticket_key_scan`: `lines_read`, each prefix with its count, and `github_refs`.\n   Drop each prefix's `examples` list before recording; never store examples, branch names or\n   commit text, or the record check refuses the scan. Then, by the top prefix's hits:\n   - One clear prefix (at least 3 hits and at least twice the next): set `setup.tracker_kind` to\n     `jira`, check that project with one read, then recommend it in one choice prompt, with a\n     different project as the other option, saying, with ABC the prefix found:\n     \"Your branches and commits mostly mention ABC tickets, so I'll use the ABC project in Jira.\"\n     If that one read fails (not found, renamed or not visible), say once why and ask instead.\n   - Several close prefixes (at least 3 hits, less than twice the next): one choice prompt, most\n     hits first, the top one recommended, plus a different project.\n   - Fewer than 3 hits: recommend nothing; ask which Jira project to use, with the prefixes found\n     as plain choices plus a different project.\n   - Only GitHub refs such as `#123`: set `setup.tracker_kind` to `github` and follow\n     `references\u002Ftracker-profiles-github.md`.\n   - Nothing found, nothing read or no list actions: ask which Jira project to use.\n   A list that errors or is cut short still counts: scan the lines read and record `lines_read`;\n   ask only when nothing was read. A failed list read never makes the repository unreadable.\n   When the keys point clearly to a Jira project but only GitHub is connected, name that Jira\n   project once and let the person choose: connect Jira now, or carry on with GitHub and export\n   the tickets. Record `setup.project_key_source` as `repository` when the person takes the\n   recommended project, and `asked` otherwise. Never search the tracker broadly to pick a project.\n3. With no readable repository, skip `scripts\u002Fcheck_onboarded.py` and check the tracker next. If the\n   tracker is readable, set `setup.evidence_level` to `tracker-only` and say once:\n   \"No repository is connected, so I'll work from the tickets in your tracker. Tickets show what was planned or asked for, not what is built.\"\n   If neither is readable, say this, invent nothing and stop:\n   \"I can't read a repository or the tracker from here, so there is nothing to ground this on. Attach the repository or its docs folder, or switch on the tracker connector, and I'll carry on.\"\n4. Check the tracker for reading and for writing separately (`references\u002Fconnect-tracker.md`).\n   Readable: one read-only search in the target project answers. Store `setup.tracker_readable`.\n   Writable: the connector offers a create action for the target project and the user can create\n   issues there (PUB-7). Store the project's issue types, required fields, link types and the size\n   and sprint field ids (PUB-1) in `setup`.\n5. If the tracker is readable but not writable, do not stop: say once, before grounding starts,\n   that the tickets will leave by export, and carry on. If it is neither, stop before drafting. Say\n   plainly what is missing (connector off, no write tools, or no create permission) and who\n   usually fixes it, and offer the export fallback (PUB-7, PUB-8).\n6. Warn once, here, that every created issue carries a run label and run labels accumulate in the\n   site's label list (PUB-4).\n\nAction names differ by connector version: resolve each from what the connector exposes, never a\nhard-coded tool name. Jira specifics: `references\u002Ftracker-profiles-jira.md`.\n\nGitHub follows `references\u002Ftracker-profiles-github.md`: GitHub Issues is export only (host GitHub\nconnectors are read only). Record the kind as GitHub, export only, and route the hand off to the\nexport fallback (PUB-7, PUB-8) without checking for a create action.\n\n## If the checks cannot run\n\nDo the onboarded check by hand:\n\n- List the `docs\u002Fmodules` folders and read each one's `index\u002Fsummary.md`. Treat an empty or\n  whitespace-only summary as missing.\n- Look for `docs\u002Finstructions\u002Fregistries\u002Fmodules.md`, the modules list; empty counts as missing.\n- project-docs (ready): the modules list plus at least one summary. docs-and-code (partly ready): a\n  summary but no modules list; carry on as above and say the exact sentence in\n  `references\u002Fconnect-repository.md` once. code-only (not set up): no summary; carry on from code by\n  names as what the code suggests, never stopping a readable-code repository. Record the level in\n  `setup.evidence_level`.\n\nWith no readable repository, skip the onboarded check: follow `references\u002Fground-from-tracker.md`\nfor the tracker-only sentence, or the stop sentence when the tracker cannot be read either.\n\nPick the Jira project by hand as in `references\u002Fconnect-tracker.md`: count the ticket key prefixes\nin the branch names and commit subjects you can see, with the same thresholds, and ask when none\nreaches 3 hits. Record only the counts in `setup.ticket_key_scan`, never the example keys.\n\nThen do the tracker checks by hand (PUB-1 and PUB-7):\n\n- Try one read-only search in the target project and record whether it answered.\n- Confirm a create-issue action exists for the target project and the user can create issues there;\n  if not, offer the export fallback, and stop only when the tracker cannot be read either.\n- Record the issue types, required fields, link types, and the size and sprint custom field ids\n  (from the issue type's full field list) in `setup`.\n\n## Output\n\nThe `setup` block: the readable sources in order (`setup.grounding_sources`), the chosen repository\n(`setup.repository`), its state (`setup.repository_state`, ready or partly-ready) and its evidence\nlevel (`setup.evidence_level`, project-docs, docs-and-code or code-only, or tracker-only with no\nrepository), whether the tracker can be read (`setup.tracker_readable`), tracker kind, project key, epic and story types,\nissue types, required fields, link types, size and sprint field ids, whether the user can create\nissues, the run label (the run id in lowercase), where the project key came from\n(`setup.project_key_source`) and the ticket key counts (`setup.ticket_key_scan`).\n","# get-connected\n\nHow to talk: follow `references\u002Fvoice.md`. Short, answer first, plain business words, no narration,\none short sources line. Those rules win.\n\nStep 0: get connected. Fills the `setup` block.\n\n## When this runs\n\nDirected by the discover journey; not started directly.\n\n## What it does\n\nWork out which sources can be read, the repository first and the tracker second, and record them in\norder in `setup.grounding_sources` (`references\u002Fground-from-tracker.md`).\n\n1. Choose and reach the repository by capability (`references\u002Fconnect-repository.md`), then detect\n   its evidence level (`references\u002Fevidence-levels.md`) with `scripts\u002Fcheck_onboarded.py`. project-docs (ready): carry on from project docs.\n   docs-and-code (partly ready): carry on, say its message once and name the areas without a summary\n   as not documented. code-only (not set up, with reachable code): carry on from code by names, as\n   what the code suggests. Stop only when nothing is readable. Store the choice in `setup.repository`, its state in `setup.repository_state`,\n   and the level in `setup.evidence_level`. When a repository connector is switched on but offers no\n   list or read action, say this once and carry on tracker only, with `setup.repository_state`\n   `connector-unreadable`:\n   \"GitHub is connected, but I can't read any repositories through it from here. I'll work from the tickets for now. To use the code and docs, attach the repository or its docs folder.\"\n   A read that fails on sign-in or a rate limit is not this case and never gets that sentence. With\n   no readable tracker either, say nothing can be read, as in step 3, and stop.\n2. Find the Jira project from the repository, before any tracker read. With no readable repository\n   skip this and ask which project to use. With the repository connector's list actions, resolved by\n   capability, read up to 100 branch names and the subjects of the last 50 commits on the default\n   branch, newest first, and pipe them one per line to `scripts\u002Ffind_ticket_keys.py`. Store only its\n   counts in `setup.ticket_key_scan`: `lines_read`, each prefix with its count, and `github_refs`.\n   Drop each prefix's `examples` list before recording; never store examples, branch names or\n   commit text, or the record check refuses the scan. Then, by the top prefix's hits:\n   - One clear prefix (at least 3 hits and at least twice the next): set `setup.tracker_kind` to\n     `jira`, check that project with one read, then recommend it in one choice prompt, with a\n     different project as the other option, saying, with ABC the prefix found:\n     \"Your branches and commits mostly mention ABC tickets, so I'll use the ABC project in Jira.\"\n     If that one read fails (not found, renamed or not visible), say once why and ask instead.\n   - Several close prefixes (at least 3 hits, less than twice the next): one choice prompt, most\n     hits first, the top one recommended, plus a different project.\n   - Fewer than 3 hits: recommend nothing; ask which Jira project to use, with the prefixes found\n     as plain choices plus a different project.\n   - Only GitHub refs such as `#123`: set `setup.tracker_kind` to `github` and follow\n     `references\u002Ftracker-profiles-github.md`.\n   - Nothing found, nothing read or no list actions: ask which Jira project to use.\n   A list that errors or is cut short still counts: scan the lines read and record `lines_read`;\n   ask only when nothing was read. A failed list read never makes the repository unreadable.\n   When the keys point clearly to a Jira project but only GitHub is connected, name that Jira\n   project once and let the person choose: connect Jira now, or carry on with GitHub and export\n   the tickets. Record `setup.project_key_source` as `repository` when the person takes the\n   recommended project, and `asked` otherwise. Never search the tracker broadly to pick a project.\n3. With no readable repository, skip `scripts\u002Fcheck_onboarded.py` and check the tracker next. If the\n   tracker is readable, set `setup.evidence_level` to `tracker-only` and say once:\n   \"No repository is connected, so I'll work from the tickets in your tracker. Tickets show what was planned or asked for, not what is built.\"\n   If neither is readable, say this, invent nothing and stop:\n   \"I can't read a repository or the tracker from here, so there is nothing to ground this on. Attach the repository or its docs folder, or switch on the tracker connector, and I'll carry on.\"\n4. Check the tracker for reading and for writing separately (`references\u002Fconnect-tracker.md`).\n   Readable: one read-only search in the target project answers. Store `setup.tracker_readable`.\n   Writable: the connector offers a create action for the target project and the user can create\n   issues there (PUB-7). Store the project's issue types, required fields, link types and the size\n   and sprint field ids (PUB-1) in `setup`.\n5. If the tracker is readable but not writable, do not stop: say once, before grounding starts,\n   that the tickets will leave by export, and carry on. If it is neither, stop before drafting. Say\n   plainly what is missing (connector off, no write tools, or no create permission) and who\n   usually fixes it, and offer the export fallback (PUB-7, PUB-8).\n6. Warn once, here, that every created issue carries a run label and run labels accumulate in the\n   site's label list (PUB-4).\n\nAction names differ by connector version: resolve each from what the connector exposes, never a\nhard-coded tool name. Jira specifics: `references\u002Ftracker-profiles-jira.md`.\n\nGitHub follows `references\u002Ftracker-profiles-github.md`: GitHub Issues is export only (host GitHub\nconnectors are read only). Record the kind as GitHub, export only, and route the hand off to the\nexport fallback (PUB-7, PUB-8) without checking for a create action.\n\n## If the checks cannot run\n\nDo the onboarded check by hand:\n\n- List the `docs\u002Fmodules` folders and read each one's `index\u002Fsummary.md`. Treat an empty or\n  whitespace-only summary as missing.\n- Look for `docs\u002Finstructions\u002Fregistries\u002Fmodules.md`, the modules list; empty counts as missing.\n- project-docs (ready): the modules list plus at least one summary. docs-and-code (partly ready): a\n  summary but no modules list; carry on as above and say the exact sentence in\n  `references\u002Fconnect-repository.md` once. code-only (not set up): no summary; carry on from code by\n  names as what the code suggests, never stopping a readable-code repository. Record the level in\n  `setup.evidence_level`.\n\nWith no readable repository, skip the onboarded check: follow `references\u002Fground-from-tracker.md`\nfor the tracker-only sentence, or the stop sentence when the tracker cannot be read either.\n\nPick the Jira project by hand as in `references\u002Fconnect-tracker.md`: count the ticket key prefixes\nin the branch names and commit subjects you can see, with the same thresholds, and ask when none\nreaches 3 hits. Record only the counts in `setup.ticket_key_scan`, never the example keys.\n\nThen do the tracker checks by hand (PUB-1 and PUB-7):\n\n- Try one read-only search in the target project and record whether it answered.\n- Confirm a create-issue action exists for the target project and the user can create issues there;\n  if not, offer the export fallback, and stop only when the tracker cannot be read either.\n- Record the issue types, required fields, link types, and the size and sprint custom field ids\n  (from the issue type's full field list) in `setup`.\n\n## Output\n\nThe `setup` block: the readable sources in order (`setup.grounding_sources`), the chosen repository\n(`setup.repository`), its state (`setup.repository_state`, ready or partly-ready) and its evidence\nlevel (`setup.evidence_level`, project-docs, docs-and-code or code-only, or tracker-only with no\nrepository), whether the tracker can be read (`setup.tracker_readable`), tracker kind, project key, epic and story types,\nissue types, required fields, link types, size and sprint field ids, whether the user can create\nissues, the run label (the run id in lowercase), where the project key came from\n(`setup.project_key_source`) and the ticket key counts (`setup.ticket_key_scan`).\n",{"name":5,"description":7,"compatibility":23},"claude.ai chat, Cowork or Claude Code; reads project docs and code through a connector, uploaded files or the open folder","main","b6381d47d62a64885cd1580ac98c0bf2607d65db","runtime\u002Fclaude-plugin\u002Fskills\u002Fget-connected",0,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai","https:\u002F\u002Fpaqad.ai","https:\u002F\u002Fgithub.com\u002FEliyce","https:\u002F\u002Feliyce.com\u002F","AI delivery you can review. Dutch software company building software and AI agents. Makers of Paqad, the open-source AI delivery framework.","2026-11-13 04:41:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Eliyce\u002Fpaqad-ai --skill get-connected",{"tool":40,"command":41},"bunx","bunx skills add Eliyce\u002Fpaqad-ai --skill get-connected",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Eliyce\u002Fpaqad-ai --skill get-connected","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,84],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fconnect-repository.md","REFERENCE","参考文档",6795,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Fconnect-repository.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fconnect-tracker.md",3842,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Fconnect-tracker.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fevidence-levels.md",5071,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Fevidence-levels.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fground-from-tracker.md",6406,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Fground-from-tracker.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ftracker-profiles-github.md",3397,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Ftracker-profiles-github.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftracker-profiles-jira.md",3167,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Ftracker-profiles-jira.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fvoice.md",4432,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Freferences\u002Fvoice.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fcheck_onboarded.py","SCRIPT","脚本",2732,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Fscripts\u002Fcheck_onboarded.py",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Ffind_ticket_keys.py",2377,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002Fscripts\u002Ffind_ticket_keys.py",[89,96,103,109,115,122],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M74FRYRD3634Z7GSTH2RSJDT","start","Chat and Claude Code: One place to start for product work, routing you to the capability that fits. Use it when you want help with product work and a single place to begin (\"help me with this ticket\", \"I have an idea\", \"what can you do here?\", \"where do I start?\"). It reads what you are after, names the capability that handles it, and hands you straight to it behind the scenes, so you only have to remember one entry. It is a thin router: it does no drafting, keeps no record, and writes nothing to the tracker itself; the capability it hands you to does that work.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fstart\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M74FPTPNDVPM80EGS2SDXBGT","ask","Chat and Claude Code: Answers business questions about the product from the project's own documentation and code, in plain words with sources. Use it when someone asks what the product is, what it does or what areas it has (\"what is this product?\", \"what does this project do?\", \"what areas does it have?\"), when a repository is attached or connected and the user asks what it is or what it does, or when they ask how something works today (\"can customers pause a subscription today?\", \"who uses the export screen?\", \"which orders go to the finance system?\"). It works on any repository at the best evidence level it can reach, reads only what the question needs, leads with the answer, adds one short Sources line and one short source line for the level, shows the project's own term on first use, and says honestly where the documents cannot confirm something. It never writes to the tracker, and it can offer to carry a question into the idea journey when the answer reveals a gap.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fask\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M74F8R3RBJEJH8ZZ4QYEVX9W","front-door","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fskills\u002Ffront-door\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M74F8B8K78VCXFQJBFCH67NX","ask-project","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fskills\u002Fask-project\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":18},"01M74FS6F5V7ZGBJ011K6ZSQSH","write-tickets","Chat and Claude Code: Step 5 of the discover journey: drafts epics and user-story tickets with Given\u002FWhen\u002FThen acceptance criteria into the ticket set and a preview. Also redrafts the ticket set and its preview when the person changes the draft during the journey, for example moving a group of tickets to a different epic or a new one, and asks for approval again. Use when the journey directs it to step 5 or back to it for a redraft, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fwrite-tickets\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":18},"01M74FRH7SCYZ5F97TRJZ2J6R4","shape-idea","Chat and Claude Code: Step 3 of the discover journey: plays the idea back with options, trade-offs and a recommendation. Use when the journey directs it to step 3, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fshape-idea\u002FSKILL.md",[],[]]