[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JFARTNN95TMV12VS453SN1":3,"skill-same:01M6JFARTNN95TMV12VS453SN1":96},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":81,"install":82,"resources":95},"01M6JFARTNN95TMV12VS453SN1","teams-meeting-pipeline",null,"Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fteams-meeting-pipeline\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"teams","meeting","pipeline","teams meeting pipeline","replay","tenant","inspect","operate","guides","app","microsoft graph","registration","manage","cli","guide","Microsoft-Graph","messaging","graph","msgraph","status","2026-11-10 10:12:30",false,"---\nname: teams-meeting-pipeline\ndescription: \"Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.\"\nversion: 1.1.0\nauthor: Hermes Agent + Teknium\nlicense: MIT\nprerequisites:\n  env_vars: [MSGRAPH_TENANT_ID, MSGRAPH_CLIENT_ID, MSGRAPH_CLIENT_SECRET]\n  commands: [hermes]\nmetadata:\n  hermes:\n    tags: [Teams, Microsoft Graph, Meetings, Productivity, Operations]\n    related_docs:\n      - \u002Fdocs\u002Fguides\u002Fmicrosoft-graph-app-registration\n      - \u002Fdocs\u002Fuser-guide\u002Fmessaging\u002Fteams-meetings\n      - \u002Fdocs\u002Fguides\u002Foperate-teams-meeting-pipeline\n---\n\n# Teams Meeting Pipeline\n\nUse this skill whenever the user asks about Microsoft Teams meeting summaries, transcripts, recordings, action items, Graph subscriptions, or any operational question about the Teams meeting pipeline. Works in any language — the triggers below are examples, not an exhaustive list.\n\nEverything operator-facing is a `hermes teams-pipeline` subcommand run via the terminal tool. There are no new model tools for this pipeline — the CLI is the surface.\n\n## When to use this skill\n\nThe user is asking to:\n- summarize a Teams meeting \u002F extract action items \u002F pull meeting notes\n- check pipeline status, inspect a stored meeting job, or see recent meetings\n- replay \u002F re-run a stored job that failed or needs a fresh summary\n- validate Microsoft Graph setup after changing env or config\n- troubleshoot \"meeting summary never arrived\" or \"no new meetings are ingesting\"\n- manage Graph webhook subscriptions (create, renew, delete, inspect)\n- set up automated subscription renewal (see pitfall below)\n\nMultilingual trigger examples (not exhaustive):\n- English: \"summarize the Teams meeting\", \"pipeline status\", \"replay job X\"\n- Turkish: \"Teams meeting özetle\", \"action item çıkar\", \"toplantı notu\", \"pipeline durumu\", \"replay job\"\n\n## Prerequisites\n\nBefore using the pipeline, verify these are set in `${HERMES_HOME:-~\u002F.hermes}\u002F.env`:\n\n```bash\nMSGRAPH_TENANT_ID=...\nMSGRAPH_CLIENT_ID=...\nMSGRAPH_CLIENT_SECRET=...\n```\n\nIf any are missing, direct the user to the Azure app registration guide at `\u002Fdocs\u002Fguides\u002Fmicrosoft-graph-app-registration` — they need an Azure AD app registration with admin-consented Graph application permissions before the pipeline will work.\n\n## Command reference\n\n### Status and inspection (start here)\n\n```bash\nhermes teams-pipeline validate              # config snapshot — run first after any change\nhermes teams-pipeline token-health          # Graph token status\nhermes teams-pipeline token-health --force-refresh   # force a fresh token acquisition\nhermes teams-pipeline list                  # recent meeting jobs\nhermes teams-pipeline list --status failed  # only failed jobs\nhermes teams-pipeline show \u003Cjob-id>         # full detail of one job\nhermes teams-pipeline subscriptions         # current Graph webhook subscriptions\n```\n\n### Re-running \u002F debugging\n\n```bash\nhermes teams-pipeline run \u003Cjob-id>          # replay a stored job (re-summarize, re-deliver)\nhermes teams-pipeline fetch --meeting-id \u003Cid>   # dry-run: resolve meeting + transcript without persisting\nhermes teams-pipeline fetch --join-web-url \"\u003Curl>\"   # dry-run by join URL\n```\n\n### Subscription management\n\n```bash\nhermes teams-pipeline subscribe \\\n  --resource communications\u002FonlineMeetings\u002FgetAllTranscripts \\\n  --notification-url https:\u002F\u002F\u003Cyour-public-host>\u002Fmsgraph\u002Fwebhook \\\n  --client-state \"$MSGRAPH_WEBHOOK_CLIENT_STATE\"\n\nhermes teams-pipeline renew-subscription \u003Csub-id> --expiration \u003Ciso-8601>\nhermes teams-pipeline delete-subscription \u003Csub-id>\nhermes teams-pipeline maintain-subscriptions            # renew near-expiry ones\nhermes teams-pipeline maintain-subscriptions --dry-run  # show what would be renewed\n```\n\n## Decision tree for common asks\n\n- User asks \"why didn't I get a summary for today's meeting?\" → start with `list --status failed`, then `show \u003Cjob-id>` on the relevant row. If the job doesn't exist at all, check `subscriptions` — the webhook may have expired (see pitfall below).\n- User asks \"is setup working?\" → `validate`, then `token-health`, then `subscriptions`. If all three pass, request a test meeting and check `list` for a fresh row.\n- User asks \"re-run summary for meeting X\" → `list` to find the job ID, `run \u003Cjob-id>` to replay. If it fails again, `show \u003Cjob-id>` to inspect the error and `fetch --meeting-id` to dry-run the artifact resolution.\n- User asks \"add meeting X to the pipeline\" → usually you don't — the pipeline is subscription-driven, not per-meeting. If they want a specific past meeting summarized, use `fetch` to pull transcript + `run` after a job is created.\n\n## Critical pitfall: Graph subscriptions expire in 72 hours\n\nMicrosoft Graph caps webhook subscriptions at 72 hours and **will not auto-renew them**. If `maintain-subscriptions` is not scheduled, meeting notifications silently stop arriving 3 days after any manual subscription creation.\n\nWhen the user reports \"the pipeline worked yesterday but nothing is arriving today\":\n1. Run `hermes teams-pipeline subscriptions` — if it's empty or all entries show `expirationDateTime` in the past, that's the cause.\n2. Recreate with `subscribe` as shown above.\n3. **Set up automated renewal immediately** via `hermes cron add`, a systemd timer, or plain crontab. The operator runbook at `\u002Fdocs\u002Fguides\u002Foperate-teams-meeting-pipeline#automating-subscription-renewal-required-for-production` has all three options. 12-hour interval is safe (6x headroom against the 72h limit).\n\n## Other pitfalls\n\n- **Transcript not available yet.** Teams takes some time after a meeting ends to generate the transcript artifact. `fetch --meeting-id` on a just-ended meeting may return empty. Wait 2-5 minutes and retry, or let the Graph webhook drive ingestion naturally.\n- **Delivery mode mismatch.** If summaries are produced (`list` shows success) but nothing lands in Teams, check `platforms.teams.extra.delivery_mode` and the matching target config (`incoming_webhook_url` OR `chat_id` OR `team_id`+`channel_id`). The writer reads these from config.yaml or `TEAMS_*` env vars.\n- **Graph app permissions.** A token acquires cleanly (`token-health` passes) but Graph API calls return 401\u002F403 when permissions were added but admin consent wasn't re-granted. Have the user revisit the app registration in the Azure portal and click \"Grant admin consent\" again.\n\n## Related docs\n\nPoint the user to these when they need more depth than this skill covers:\n- Azure app registration walkthrough: `\u002Fdocs\u002Fguides\u002Fmicrosoft-graph-app-registration`\n- Full pipeline setup: `\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002Fteams-meetings`\n- Operator runbook (renewal automation, troubleshooting, go-live checklist): `\u002Fdocs\u002Fguides\u002Foperate-teams-meeting-pipeline`\n- Webhook listener setup: `\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002Fmsgraph-webhook`\n","# Teams Meeting Pipeline\n\nUse this skill whenever the user asks about Microsoft Teams meeting summaries, transcripts, recordings, action items, Graph subscriptions, or any operational question about the Teams meeting pipeline. Works in any language — the triggers below are examples, not an exhaustive list.\n\nEverything operator-facing is a `hermes teams-pipeline` subcommand run via the terminal tool. There are no new model tools for this pipeline — the CLI is the surface.\n\n## When to use this skill\n\nThe user is asking to:\n- summarize a Teams meeting \u002F extract action items \u002F pull meeting notes\n- check pipeline status, inspect a stored meeting job, or see recent meetings\n- replay \u002F re-run a stored job that failed or needs a fresh summary\n- validate Microsoft Graph setup after changing env or config\n- troubleshoot \"meeting summary never arrived\" or \"no new meetings are ingesting\"\n- manage Graph webhook subscriptions (create, renew, delete, inspect)\n- set up automated subscription renewal (see pitfall below)\n\nMultilingual trigger examples (not exhaustive):\n- English: \"summarize the Teams meeting\", \"pipeline status\", \"replay job X\"\n- Turkish: \"Teams meeting özetle\", \"action item çıkar\", \"toplantı notu\", \"pipeline durumu\", \"replay job\"\n\n## Prerequisites\n\nBefore using the pipeline, verify these are set in `${HERMES_HOME:-~\u002F.hermes}\u002F.env`:\n\n```bash\nMSGRAPH_TENANT_ID=...\nMSGRAPH_CLIENT_ID=...\nMSGRAPH_CLIENT_SECRET=...\n```\n\nIf any are missing, direct the user to the Azure app registration guide at `\u002Fdocs\u002Fguides\u002Fmicrosoft-graph-app-registration` — they need an Azure AD app registration with admin-consented Graph application permissions before the pipeline will work.\n\n## Command reference\n\n### Status and inspection (start here)\n\n```bash\nhermes teams-pipeline validate              # config snapshot — run first after any change\nhermes teams-pipeline token-health          # Graph token status\nhermes teams-pipeline token-health --force-refresh   # force a fresh token acquisition\nhermes teams-pipeline list                  # recent meeting jobs\nhermes teams-pipeline list --status failed  # only failed jobs\nhermes teams-pipeline show \u003Cjob-id>         # full detail of one job\nhermes teams-pipeline subscriptions         # current Graph webhook subscriptions\n```\n\n### Re-running \u002F debugging\n\n```bash\nhermes teams-pipeline run \u003Cjob-id>          # replay a stored job (re-summarize, re-deliver)\nhermes teams-pipeline fetch --meeting-id \u003Cid>   # dry-run: resolve meeting + transcript without persisting\nhermes teams-pipeline fetch --join-web-url \"\u003Curl>\"   # dry-run by join URL\n```\n\n### Subscription management\n\n```bash\nhermes teams-pipeline subscribe \\\n  --resource communications\u002FonlineMeetings\u002FgetAllTranscripts \\\n  --notification-url https:\u002F\u002F\u003Cyour-public-host>\u002Fmsgraph\u002Fwebhook \\\n  --client-state \"$MSGRAPH_WEBHOOK_CLIENT_STATE\"\n\nhermes teams-pipeline renew-subscription \u003Csub-id> --expiration \u003Ciso-8601>\nhermes teams-pipeline delete-subscription \u003Csub-id>\nhermes teams-pipeline maintain-subscriptions            # renew near-expiry ones\nhermes teams-pipeline maintain-subscriptions --dry-run  # show what would be renewed\n```\n\n## Decision tree for common asks\n\n- User asks \"why didn't I get a summary for today's meeting?\" → start with `list --status failed`, then `show \u003Cjob-id>` on the relevant row. If the job doesn't exist at all, check `subscriptions` — the webhook may have expired (see pitfall below).\n- User asks \"is setup working?\" → `validate`, then `token-health`, then `subscriptions`. If all three pass, request a test meeting and check `list` for a fresh row.\n- User asks \"re-run summary for meeting X\" → `list` to find the job ID, `run \u003Cjob-id>` to replay. If it fails again, `show \u003Cjob-id>` to inspect the error and `fetch --meeting-id` to dry-run the artifact resolution.\n- User asks \"add meeting X to the pipeline\" → usually you don't — the pipeline is subscription-driven, not per-meeting. If they want a specific past meeting summarized, use `fetch` to pull transcript + `run` after a job is created.\n\n## Critical pitfall: Graph subscriptions expire in 72 hours\n\nMicrosoft Graph caps webhook subscriptions at 72 hours and **will not auto-renew them**. If `maintain-subscriptions` is not scheduled, meeting notifications silently stop arriving 3 days after any manual subscription creation.\n\nWhen the user reports \"the pipeline worked yesterday but nothing is arriving today\":\n1. Run `hermes teams-pipeline subscriptions` — if it's empty or all entries show `expirationDateTime` in the past, that's the cause.\n2. Recreate with `subscribe` as shown above.\n3. **Set up automated renewal immediately** via `hermes cron add`, a systemd timer, or plain crontab. The operator runbook at `\u002Fdocs\u002Fguides\u002Foperate-teams-meeting-pipeline#automating-subscription-renewal-required-for-production` has all three options. 12-hour interval is safe (6x headroom against the 72h limit).\n\n## Other pitfalls\n\n- **Transcript not available yet.** Teams takes some time after a meeting ends to generate the transcript artifact. `fetch --meeting-id` on a just-ended meeting may return empty. Wait 2-5 minutes and retry, or let the Graph webhook drive ingestion naturally.\n- **Delivery mode mismatch.** If summaries are produced (`list` shows success) but nothing lands in Teams, check `platforms.teams.extra.delivery_mode` and the matching target config (`incoming_webhook_url` OR `chat_id` OR `team_id`+`channel_id`). The writer reads these from config.yaml or `TEAMS_*` env vars.\n- **Graph app permissions.** A token acquires cleanly (`token-health` passes) but Graph API calls return 401\u002F403 when permissions were added but admin consent wasn't re-granted. Have the user revisit the app registration in the Azure portal and click \"Grant admin consent\" again.\n\n## Related docs\n\nPoint the user to these when they need more depth than this skill covers:\n- Azure app registration walkthrough: `\u002Fdocs\u002Fguides\u002Fmicrosoft-graph-app-registration`\n- Full pipeline setup: `\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002Fteams-meetings`\n- Operator runbook (renewal automation, troubleshooting, go-live checklist): `\u002Fdocs\u002Fguides\u002Foperate-teams-meeting-pipeline`\n- Webhook listener setup: `\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002Fmsgraph-webhook`\n",{"name":5,"author":53,"license":14,"version":54,"metadata":55,"description":7,"prerequisites":67},"Hermes Agent + Teknium","1.1.0",{"hermes":56},{"tags":57,"related_docs":63},[58,59,60,61,62],"Teams","Microsoft Graph","Meetings","Productivity","Operations",[64,65,66],"\u002Fdocs\u002Fguides\u002Fmicrosoft-graph-app-registration","\u002Fdocs\u002Fuser-guide\u002Fmessaging\u002Fteams-meetings","\u002Fdocs\u002Fguides\u002Foperate-teams-meeting-pipeline",{"commands":68,"env_vars":70},[69],"hermes",[71,72,73],"MSGRAPH_TENANT_ID","MSGRAPH_CLIENT_ID","MSGRAPH_CLIENT_SECRET","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fproductivity\u002Fteams-meeting-pipeline",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":83,"prompt":93,"zipAvailable":94},[84,87,90],{"tool":85,"command":86},"npx","npx skills add S3YED\u002Fappie-kit --skill teams-meeting-pipeline",{"tool":88,"command":89},"bunx","bunx skills add S3YED\u002Fappie-kit --skill teams-meeting-pipeline",{"tool":91,"command":92},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill teams-meeting-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fproductivity\u002Fteams-meeting-pipeline\u002FSKILL.md",true,[],[97,128,161,187,217,242],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":110,"publishedAt":48},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[103,106,109],{"categoryNo":104,"categoryName":105,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":107,"categoryName":108,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[111,112,113,114,115,116,69,117,118,119,120,121,122,123,124,125,126,127],"music","ai music","humanizer","visualization","Tools","Audio","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":140,"publishedAt":48},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[134,137],{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":138,"categoryName":139,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师",[141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":169,"publishedAt":48},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[167,168],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":138,"categoryName":139,"taxonomyType":25,"taxonomyTypeDesc":26},[142,170,146,171,172,173,148,174,175,176,177,178,179,180,181,182,183,184,185,186],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":197,"publishedAt":48},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[198,199,200,201,41,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216],"deployment","vercel deployment","vercel","macos","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":48},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[223],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification","for",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":255,"publishedAt":48},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[248,251,254],{"categoryNo":249,"categoryName":250,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":252,"categoryName":253,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[256,257,258,259,260,261,262,263,201,264,265,148,266,203,267,234,268,269,270,271],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]