[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JWZAX83F55MKQHJSSVHS1":3,"skill-same:01M75JWZAX83F55MKQHJSSVHS1":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75JWZAX83F55MKQHJSSVHS1","simplified-architect",null,"Use only when the user explicitly says \"simple architect\".","LiorZivi\u002FZiviDevelopmentMarketplace","LiorZivi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20906364?v=4","01M75JSA2QYQCR1ZNNQ16G1ZBG","01M75JSA3RWE8SXTCDVKK8H5TA",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-ai\u002Fskills\u002Fsimplified-architect\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: simplified-architect\ndescription: Use only when the user explicitly says \"simple architect\".\n---\n\n# Simplified Architect\n\nCreate a PM-level spec and a phased implementation plan directly through two deliberate rounds of user questioning.\n\n## Shared guidance\n\n- Spec rules: `..\u002F..\u002Freferences\u002Fspec-guidance.md`\n- Plan rules: `..\u002F..\u002Freferences\u002Fplan-guidance.md`\n\nRead both files before drafting or revising artifacts.\n\n## Paths\n\n- Output directory: `.\u002Foutput\u002Farchitect\u002F`\n- `{PlanName}` is PascalCase derived from the task.\n- Spec: `.\u002Foutput\u002Farchitect\u002F{PlanName}-spec.md`\n- Plan: `.\u002Foutput\u002Farchitect\u002F{PlanName}-plan.md`\n\n## Core planning principle\n\nPrefer the simplest clean design that satisfies the confirmed goal.\n\nWhen broader scenario coverage, defensive flexibility, or an edge case would make the design harder to understand or implement:\n\n1. Treat it as out of scope in the default design.\n2. Record and explain the resulting gap plainly.\n3. Ask whether the user wants that gap promoted into scope.\n4. Add the complexity only when the user chooses it or the confirmed goal cannot work safely without it.\n\nDo not silently ignore correctness, security, data-loss, or compatibility requirements. Simplicity means avoiding speculative complexity, not accepting a broken design.\n\n## Mode detection\n\n- **Create**: no matching spec and plan exist. Run the full workflow.\n- **Revise**: matching artifacts exist. Read them, interview the user about the requested change, and revise both when product intent changes.\n\n## Workflow\n\n### 1. Scan the workspace\n\nInspect the relevant repository structure, code, tests, configuration, documentation, and existing patterns. Learn technical facts from the workspace rather than asking the user to supply them.\n\n### 2. First questioning round: understand the purpose\n\nAsk one question at a time through the host picker. Prefer choices when they capture the real decision; use free text when they do not.\n\nContinue until all material areas are clear:\n\n- Goal and problem being solved\n- Users and audience\n- User-visible behavior\n- Scope and non-goals\n- Success criteria\n- Constraints and integrations\n- Behavioral defaults\n- Compatibility or migration expectations\n- Failure behavior and meaningful risks\n- Simplicity trade-offs and intentionally uncovered edge cases\n\nQuestions should be thorough, grounded in the scan, and limited to decisions only the user can make. Do not impose a fixed question count or stop because a small quota was reached.\n\nBefore drafting, summarize the understood intent internally and check that no answer conflicts with another. Ask another question whenever the purpose or acceptance boundary is still ambiguous.\n\n### 3. Draft the spec and plan\n\nWrite both artifacts using the shared guidance.\n\nUse `Pragmatic` as the plan approach unless the user explicitly requests another label. Keep the plan focused on the simplest implementation that fulfills the spec. Put excluded scenarios in the spec's Non-Goals and any implementation consequence in plan risks or open questions.\n\n### 4. Second questioning round: challenge the drafts\n\nRead the complete draft spec and plan together. Look for:\n\n- Assumptions that became visible only after decomposition\n- Conflicts between product intent and implementation steps\n- Missing acceptance boundaries\n- Dependencies or migrations that change the scope\n- Edge cases whose omission creates a meaningful gap\n- Places where a simpler design is possible\n- Places where the simple path has a trade-off the user should consciously accept\n\nAsk one focused question at a time about every material decision found. Always perform this round; if the drafts expose no unresolved decision, ask the user to confirm the summarized simple path and its explicitly listed gaps.\n\n### 5. Revise both artifacts\n\nApply the second-round answers to both spec and plan wherever relevant. Re-run the shared pre-write checklists and fix contradictions, stale open questions, and scope drift.\n\nAfter revision, proceed directly to the report without adding a review score.\n\n### 6. Report\n\nReport:\n\n- Spec and plan paths\n- Brief phase and step counts\n- The chosen simple approach\n- Edge cases or scenarios intentionally left out\n- Any unresolved question that the user explicitly deferred\n\n## Communication\n\n- Ask every user question through the host picker.\n- Ask exactly one question per picker call.\n- Keep progress updates brief.\n","# Simplified Architect\n\nCreate a PM-level spec and a phased implementation plan directly through two deliberate rounds of user questioning.\n\n## Shared guidance\n\n- Spec rules: `..\u002F..\u002Freferences\u002Fspec-guidance.md`\n- Plan rules: `..\u002F..\u002Freferences\u002Fplan-guidance.md`\n\nRead both files before drafting or revising artifacts.\n\n## Paths\n\n- Output directory: `.\u002Foutput\u002Farchitect\u002F`\n- `{PlanName}` is PascalCase derived from the task.\n- Spec: `.\u002Foutput\u002Farchitect\u002F{PlanName}-spec.md`\n- Plan: `.\u002Foutput\u002Farchitect\u002F{PlanName}-plan.md`\n\n## Core planning principle\n\nPrefer the simplest clean design that satisfies the confirmed goal.\n\nWhen broader scenario coverage, defensive flexibility, or an edge case would make the design harder to understand or implement:\n\n1. Treat it as out of scope in the default design.\n2. Record and explain the resulting gap plainly.\n3. Ask whether the user wants that gap promoted into scope.\n4. Add the complexity only when the user chooses it or the confirmed goal cannot work safely without it.\n\nDo not silently ignore correctness, security, data-loss, or compatibility requirements. Simplicity means avoiding speculative complexity, not accepting a broken design.\n\n## Mode detection\n\n- **Create**: no matching spec and plan exist. Run the full workflow.\n- **Revise**: matching artifacts exist. Read them, interview the user about the requested change, and revise both when product intent changes.\n\n## Workflow\n\n### 1. Scan the workspace\n\nInspect the relevant repository structure, code, tests, configuration, documentation, and existing patterns. Learn technical facts from the workspace rather than asking the user to supply them.\n\n### 2. First questioning round: understand the purpose\n\nAsk one question at a time through the host picker. Prefer choices when they capture the real decision; use free text when they do not.\n\nContinue until all material areas are clear:\n\n- Goal and problem being solved\n- Users and audience\n- User-visible behavior\n- Scope and non-goals\n- Success criteria\n- Constraints and integrations\n- Behavioral defaults\n- Compatibility or migration expectations\n- Failure behavior and meaningful risks\n- Simplicity trade-offs and intentionally uncovered edge cases\n\nQuestions should be thorough, grounded in the scan, and limited to decisions only the user can make. Do not impose a fixed question count or stop because a small quota was reached.\n\nBefore drafting, summarize the understood intent internally and check that no answer conflicts with another. Ask another question whenever the purpose or acceptance boundary is still ambiguous.\n\n### 3. Draft the spec and plan\n\nWrite both artifacts using the shared guidance.\n\nUse `Pragmatic` as the plan approach unless the user explicitly requests another label. Keep the plan focused on the simplest implementation that fulfills the spec. Put excluded scenarios in the spec's Non-Goals and any implementation consequence in plan risks or open questions.\n\n### 4. Second questioning round: challenge the drafts\n\nRead the complete draft spec and plan together. Look for:\n\n- Assumptions that became visible only after decomposition\n- Conflicts between product intent and implementation steps\n- Missing acceptance boundaries\n- Dependencies or migrations that change the scope\n- Edge cases whose omission creates a meaningful gap\n- Places where a simpler design is possible\n- Places where the simple path has a trade-off the user should consciously accept\n\nAsk one focused question at a time about every material decision found. Always perform this round; if the drafts expose no unresolved decision, ask the user to confirm the summarized simple path and its explicitly listed gaps.\n\n### 5. Revise both artifacts\n\nApply the second-round answers to both spec and plan wherever relevant. Re-run the shared pre-write checklists and fix contradictions, stale open questions, and scope drift.\n\nAfter revision, proceed directly to the report without adding a review score.\n\n### 6. Report\n\nReport:\n\n- Spec and plan paths\n- Brief phase and step counts\n- The chosen simple approach\n- Edge cases or scenarios intentionally left out\n- Any unresolved question that the user explicitly deferred\n\n## Communication\n\n- Ask every user question through the host picker.\n- Ask exactly one question per picker call.\n- Keep progress updates brief.\n",{"name":5,"description":7},"main","b0ad4fe6bb632e7113e406e43ecab014c27535df","plugins\u002Fagentic-ai\u002Fskills\u002Fsimplified-architect",0,"https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace","https:\u002F\u002Fgithub.com\u002FLiorZivi","2026-11-07 21:50:56",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add LiorZivi\u002FZiviDevelopmentMarketplace --skill simplified-architect",{"tool":36,"command":37},"bunx","bunx skills add LiorZivi\u002FZiviDevelopmentMarketplace --skill simplified-architect",{"tool":39,"command":40},"pnpm","pnpm dlx skills add LiorZivi\u002FZiviDevelopmentMarketplace --skill simplified-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-ai\u002Fskills\u002Fsimplified-architect\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"evals\u002Fevals.json","REFERENCE","参考文档",2291,"https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-ai\u002Fskills\u002Fsimplified-architect\u002Fevals\u002Fevals.json",[51,58,63,72,80,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M75JZ4GKYCD3RBB0VH9SZJKX","my-skill","SKILL_DESCRIPTION — when should Claude load this skill?","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Ftemplates\u002Fplugin-full\u002Fskills\u002Fmy-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75JZ345QQFV2NHYWFQSTTQG","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Ftemplates\u002Fplugin-basic\u002Fskills\u002Fmy-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M75JYVVAS823VXX1KC5P0R2Q","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","MIT","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fremote-plugin-blader\u002Fskills\u002Fhumanizer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fremote-plugin-blader\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75JYPHMG5V58X4CW4FAA6M6","deep-research","Use when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation. Triggers on \"deep research\", \"comprehensive analysis\", \"research report\", \"compare X vs Y\", \"analyze trends\", or \"state of the art\". Not for simple lookups, debugging, or questions answerable with 1-2 searches.","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fremote-plugin-199-biotechnologies\u002Fskills\u002Fdeep-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fremote-plugin-199-biotechnologies\u002Fskills\u002Fdeep-research\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75JYDYT6EBNY4SYMCG0MWP8","ai-local-diffusion-invoker","Generate images locally on the user's own NVIDIA GPU by invoking a separately-installed LocalAIExecution `localai` CLI (FLUX text-to-image) through its stable --json subprocess contract. This skill vendors NONE of LocalAIExecution's code — it discovers the external tool at runtime and shells out to it. Use when the user wants to create\u002Fgenerate an image, render a picture from a text prompt, run local text-to-image \u002F diffusion \u002F FLUX, or make art on their own GPU without cloud or paid APIs. Triggers on: 'generate an image of X', 'create a picture of X', 'render X locally', 'make art of X', 'text-to-image X', 'run FLUX on X', 'local diffusion X'.","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Flocal-ai\u002Fskills\u002Fai-local-diffusion-invoker\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75JY5TANS9YPMHBH0DANXGM","telegram-remote","Activate, operate, and tear down a bidirectional bridge between this Copilot CLI session and a Telegram bot DM so the user can step away from the terminal. Works from any repository and needs only a Telegram bot token plus chat ID. Posts meaningful progress, routes questions, uploads requested local files, and injects Telegram replies back into the session. Invoke with no args to activate or with 'end' to close an active session. Activation triggers: 'telegram-remote', 'i'm stepping away', 'ping me on telegram', 'post progress to telegram', 'afk mode', 'continue on telegram', 'headed into a meeting'. End triggers: 'telegram-remote end', 'end-telegram-remote', 'stop-telegram-remote', 'i'm back at the terminal', 'back from afk', 'stop posting to telegram', 'disable remote mode'.","https:\u002F\u002Fgithub.com\u002FLiorZivi\u002FZiviDevelopmentMarketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fgeneral-ops\u002Fskills\u002Ftelegram-remote\u002FSKILL.md",[],[]]