[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J7K2DRTY7K23V2J36K8EMK":3,"skill-same:01M6J7K2DRTY7K23V2J36K8EMK":94},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6J7K2DRTY7K23V2J36K8EMK","oma-pm",null,"Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.","gracefullight\u002Fkaltura-downloader","gracefullight","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11773683?v=4","01M6J7GSY7FXW67X6ZKN19ZPZZ","Eunkwang Shin","01M6J7GT2CQACSHSFZAS5FCN4C",1,"MIT","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"oma pm","pm","dependencies","for","manager","with","actionable","scope","iso","recommendations","requirements","tasks","priorities","task","specification","use","Product Manager","prioritization","product","planning","2026-11-10 10:12:30",false,"---\nname: oma-pm\ndescription: Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.\n---\n\n# PM Agent - Product Manager\n\n## Scheduling\n\n### Goal\nTurn ambiguous or complex product requests into actionable, dependency-aware plans with clear tasks, priorities, acceptance criteria, API contracts, and risk\u002Fgovernance notes.\n\n### Intent signature\n- User asks for planning, requirements, specification, scope, prioritization, task breakdown, roadmap, or implementation plan.\n- User needs work decomposed for specialist agents or orchestrator execution.\n\n### When to use\n- Breaking down complex feature requests into tasks\n- Determining technical feasibility and architecture\n- Prioritizing work and planning sprints\n- Defining API contracts and data models\n\n### When NOT to use\n- Implementing actual code -> delegate to specialized agents\n- Performing code reviews -> use QA Agent\n\n### Expected inputs\n- User request, product goal, constraints, target users, and acceptance expectations\n- Existing codebase context, architecture constraints, and integration points\n- Optional standards, risk, governance, or orchestration requirements\n\n### Expected outputs\n- JSON plan and `task-board.md`-compatible task breakdown\n- Agent assignment, title, priority, dependencies, acceptance criteria, security\u002Ftesting expectations\n- API contracts or data model sketches when relevant\n- Saved plan artifacts under `.agents\u002Fresults\u002F`\n\n```yaml\noutputs:\n  - name: plan\n    description: PM task breakdown JSON for orchestrator consumption\n    artifact: \".agents\u002Fresults\u002Fplan-*.json\"\n    required: true\n```\n\n### Dependencies\n- `resources\u002Fexecution-protocol.md`, examples, task template, and ISO planning guide\n- Shared API contract references and project context-loading rules\n- Downstream specialist skills for implementation\n\n### Control-flow features\n- Branches by ambiguity, dependency structure, risk level, and whether standards\u002Fgovernance framing is needed\n- Produces planning artifacts rather than code\n- Optimizes for parallelizable specialist-agent execution\n\n## Structural Flow\n\n### Entry\n1. Clarify the product goal, constraints, and target deliverables.\n2. Identify technical domains and required contracts.\n3. Decide whether ISO\u002Frisk\u002Fgovernance framing is relevant.\n\n### Scenes\n1. **PREPARE**: Gather requirements, constraints, and context.\n2. **REASON**: Decompose work, identify dependencies, risks, and API\u002Fdata contracts.\n3. **ACT**: Produce JSON plan and task-board-compatible output.\n4. **VERIFY**: Check task atomicity, acceptance criteria, security\u002Ftesting coverage, and dependency shape.\n5. **FINALIZE**: Save plan artifacts and summarize execution path.\n\n### Transitions\n- If requirements are ambiguous, clarify before decomposition.\n- If tasks are tightly coupled, refine contracts or sequencing.\n- If architecture is uncertain, coordinate with architecture before implementation planning.\n- If the user needs automated execution, hand off to orchestrator after plan approval.\n\n### Failure and recovery\n- If scope is too broad, split into phases.\n- If acceptance criteria are vague, rewrite them into testable outcomes.\n- If dependencies block parallel execution, surface sequencing explicitly.\n\n### Exit\n- Success: plan is actionable, testable, prioritized, and compatible with orchestrator execution.\n- Partial success: unresolved assumptions or dependencies are explicit.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|--------|---------------|----------|\n| Read requirements\u002Fcontext | `READ` | User request and project context |\n| Select planning structure | `SELECT` | Task template and workflow needs |\n| Infer tasks and dependencies | `INFER` | Domain decomposition |\n| Validate acceptance criteria | `VALIDATE` | Checklist and task schema |\n| Write plan artifacts | `WRITE` | JSON plan and task-board markdown |\n| Notify plan summary | `NOTIFY` | Final planning report |\n\n### Tools and instruments\n- Task template, examples, ISO planning guide, shared API contracts\n- Local filesystem for result artifacts\n\n### Canonical workflow path\n```text\n1. Define API\u002Fdata contracts.\n2. Decompose tasks with agent, title, priority, dependencies, and acceptance criteria.\n3. Save `.agents\u002Fresults\u002Fplan-{sessionId}.json` and `.agents\u002Fresults\u002Fresult-pm.md`.\n```\n\n### Resource scope\n| Scope | Resource target |\n|-------|-----------------|\n| `MEMORY` | Requirements, assumptions, dependencies |\n| `LOCAL_FS` | `.agents\u002Fresults\u002Fplan-{sessionId}.json`, `.agents\u002Fresults\u002Fresult-pm.md` |\n| `CODEBASE` | Optional project context and API\u002Fdata model references |\n\n### Preconditions\n- Product goal and planning boundary are sufficiently clear.\n- Required implementation domains can be identified.\n\n### Effects and side effects\n- Creates plan artifacts and task boards.\n- Influences downstream agent assignments and execution order.\n- Does not directly implement code.\n\n### Guardrails\n1. API-first design: define contracts before implementation tasks\n2. Every task has: agent, title, acceptance criteria, priority tier (1 = independent, lower runs first), dependencies, scope\n3. Minimize dependencies for maximum parallel execution\n4. Security and testing are part of every task (not separate phases)\n5. Tasks should be completable by a single agent\n6. Output JSON plan + task-board.md for orchestrator compatibility\n7. When relevant, structure plans using ISO 21500 concepts, risk prioritization using ISO 31000 thinking, and responsibility\u002Fgovernance suggestions inspired by ISO 38500\n\n### Common Pitfalls\n- Too Granular: \"Implement user auth API\" is one task, not five\n- Vague Tasks: \"Make it better\" -> \"Add loading states to all forms\"\n- Tight Coupling: tasks should use public APIs, not internal state\n- Deferred Quality: testing is part of every task, not a final phase\n\n## References\nFollow `resources\u002Fexecution-protocol.md` step by step.\nSee `resources\u002Fexamples.md` for input\u002Foutput examples.\nUse `resources\u002Fiso-planning.md` when the user needs standards-based planning, risk framing, or governance-oriented recommendations.\nSave plan to `.agents\u002Fresults\u002Fplan-{sessionId}.json` and `.agents\u002Fresults\u002Fresult-pm.md`.\nVendor-specific execution protocols are injected automatically by `oma agent:spawn`.\nSource files live under `..\u002F_shared\u002Fruntime\u002Fexecution-protocols\u002F{vendor}.md`.\n- Execution steps: `resources\u002Fexecution-protocol.md`\n- Plan examples: `resources\u002Fexamples.md`\n- ISO planning guide: `resources\u002Fiso-planning.md`\n- Error recovery: `resources\u002Ferror-playbook.md`\n- Task schema: `resources\u002Ftask-template.json`\n- Ultrawork PLAN phase protocol: `resources\u002Fplan-phase-protocol.md` (used when this skill runs inside the ultrawork workflow)\n- Task board spec (orchestrator-consumed format): `..\u002Foma-orchestrator\u002Fresources\u002Fmemory-schema.md`\n- Human-readable tracker: when running inside the `\u002Fplan` workflow, also generate `docs\u002Fplans\u002Fwork\u002F{NNN}-{name}.md` per `.agents\u002Fworkflows\u002Fplan.md`\n- API contract template (SSOT): `..\u002F_shared\u002Fcore\u002Fapi-contracts\u002Ftemplate.md`; write generated contracts to `.agents\u002Fresults\u002Fapi-contracts\u002F` (run artifact) or `docs\u002Fplans\u002Fcontracts\u002F` (durable spec)\n- Context loading: `..\u002F_shared\u002Fcore\u002Fcontext-loading.md`\n- Reasoning templates: `..\u002F_shared\u002Fcore\u002Freasoning-templates.md`\n- Clarification: `..\u002F_shared\u002Fcore\u002Fclarification-protocol.md`\n- Context budget: `..\u002F_shared\u002Fcore\u002Fcontext-budget.md`\n- Lessons learned: `..\u002F_shared\u002Fcore\u002Flessons-learned.md`\n","# PM Agent - Product Manager\n\n## Scheduling\n\n### Goal\nTurn ambiguous or complex product requests into actionable, dependency-aware plans with clear tasks, priorities, acceptance criteria, API contracts, and risk\u002Fgovernance notes.\n\n### Intent signature\n- User asks for planning, requirements, specification, scope, prioritization, task breakdown, roadmap, or implementation plan.\n- User needs work decomposed for specialist agents or orchestrator execution.\n\n### When to use\n- Breaking down complex feature requests into tasks\n- Determining technical feasibility and architecture\n- Prioritizing work and planning sprints\n- Defining API contracts and data models\n\n### When NOT to use\n- Implementing actual code -> delegate to specialized agents\n- Performing code reviews -> use QA Agent\n\n### Expected inputs\n- User request, product goal, constraints, target users, and acceptance expectations\n- Existing codebase context, architecture constraints, and integration points\n- Optional standards, risk, governance, or orchestration requirements\n\n### Expected outputs\n- JSON plan and `task-board.md`-compatible task breakdown\n- Agent assignment, title, priority, dependencies, acceptance criteria, security\u002Ftesting expectations\n- API contracts or data model sketches when relevant\n- Saved plan artifacts under `.agents\u002Fresults\u002F`\n\n```yaml\noutputs:\n  - name: plan\n    description: PM task breakdown JSON for orchestrator consumption\n    artifact: \".agents\u002Fresults\u002Fplan-*.json\"\n    required: true\n```\n\n### Dependencies\n- `resources\u002Fexecution-protocol.md`, examples, task template, and ISO planning guide\n- Shared API contract references and project context-loading rules\n- Downstream specialist skills for implementation\n\n### Control-flow features\n- Branches by ambiguity, dependency structure, risk level, and whether standards\u002Fgovernance framing is needed\n- Produces planning artifacts rather than code\n- Optimizes for parallelizable specialist-agent execution\n\n## Structural Flow\n\n### Entry\n1. Clarify the product goal, constraints, and target deliverables.\n2. Identify technical domains and required contracts.\n3. Decide whether ISO\u002Frisk\u002Fgovernance framing is relevant.\n\n### Scenes\n1. **PREPARE**: Gather requirements, constraints, and context.\n2. **REASON**: Decompose work, identify dependencies, risks, and API\u002Fdata contracts.\n3. **ACT**: Produce JSON plan and task-board-compatible output.\n4. **VERIFY**: Check task atomicity, acceptance criteria, security\u002Ftesting coverage, and dependency shape.\n5. **FINALIZE**: Save plan artifacts and summarize execution path.\n\n### Transitions\n- If requirements are ambiguous, clarify before decomposition.\n- If tasks are tightly coupled, refine contracts or sequencing.\n- If architecture is uncertain, coordinate with architecture before implementation planning.\n- If the user needs automated execution, hand off to orchestrator after plan approval.\n\n### Failure and recovery\n- If scope is too broad, split into phases.\n- If acceptance criteria are vague, rewrite them into testable outcomes.\n- If dependencies block parallel execution, surface sequencing explicitly.\n\n### Exit\n- Success: plan is actionable, testable, prioritized, and compatible with orchestrator execution.\n- Partial success: unresolved assumptions or dependencies are explicit.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|--------|---------------|----------|\n| Read requirements\u002Fcontext | `READ` | User request and project context |\n| Select planning structure | `SELECT` | Task template and workflow needs |\n| Infer tasks and dependencies | `INFER` | Domain decomposition |\n| Validate acceptance criteria | `VALIDATE` | Checklist and task schema |\n| Write plan artifacts | `WRITE` | JSON plan and task-board markdown |\n| Notify plan summary | `NOTIFY` | Final planning report |\n\n### Tools and instruments\n- Task template, examples, ISO planning guide, shared API contracts\n- Local filesystem for result artifacts\n\n### Canonical workflow path\n```text\n1. Define API\u002Fdata contracts.\n2. Decompose tasks with agent, title, priority, dependencies, and acceptance criteria.\n3. Save `.agents\u002Fresults\u002Fplan-{sessionId}.json` and `.agents\u002Fresults\u002Fresult-pm.md`.\n```\n\n### Resource scope\n| Scope | Resource target |\n|-------|-----------------|\n| `MEMORY` | Requirements, assumptions, dependencies |\n| `LOCAL_FS` | `.agents\u002Fresults\u002Fplan-{sessionId}.json`, `.agents\u002Fresults\u002Fresult-pm.md` |\n| `CODEBASE` | Optional project context and API\u002Fdata model references |\n\n### Preconditions\n- Product goal and planning boundary are sufficiently clear.\n- Required implementation domains can be identified.\n\n### Effects and side effects\n- Creates plan artifacts and task boards.\n- Influences downstream agent assignments and execution order.\n- Does not directly implement code.\n\n### Guardrails\n1. API-first design: define contracts before implementation tasks\n2. Every task has: agent, title, acceptance criteria, priority tier (1 = independent, lower runs first), dependencies, scope\n3. Minimize dependencies for maximum parallel execution\n4. Security and testing are part of every task (not separate phases)\n5. Tasks should be completable by a single agent\n6. Output JSON plan + task-board.md for orchestrator compatibility\n7. When relevant, structure plans using ISO 21500 concepts, risk prioritization using ISO 31000 thinking, and responsibility\u002Fgovernance suggestions inspired by ISO 38500\n\n### Common Pitfalls\n- Too Granular: \"Implement user auth API\" is one task, not five\n- Vague Tasks: \"Make it better\" -> \"Add loading states to all forms\"\n- Tight Coupling: tasks should use public APIs, not internal state\n- Deferred Quality: testing is part of every task, not a final phase\n\n## References\nFollow `resources\u002Fexecution-protocol.md` step by step.\nSee `resources\u002Fexamples.md` for input\u002Foutput examples.\nUse `resources\u002Fiso-planning.md` when the user needs standards-based planning, risk framing, or governance-oriented recommendations.\nSave plan to `.agents\u002Fresults\u002Fplan-{sessionId}.json` and `.agents\u002Fresults\u002Fresult-pm.md`.\nVendor-specific execution protocols are injected automatically by `oma agent:spawn`.\nSource files live under `..\u002F_shared\u002Fruntime\u002Fexecution-protocols\u002F{vendor}.md`.\n- Execution steps: `resources\u002Fexecution-protocol.md`\n- Plan examples: `resources\u002Fexamples.md`\n- ISO planning guide: `resources\u002Fiso-planning.md`\n- Error recovery: `resources\u002Ferror-playbook.md`\n- Task schema: `resources\u002Ftask-template.json`\n- Ultrawork PLAN phase protocol: `resources\u002Fplan-phase-protocol.md` (used when this skill runs inside the ultrawork workflow)\n- Task board spec (orchestrator-consumed format): `..\u002Foma-orchestrator\u002Fresources\u002Fmemory-schema.md`\n- Human-readable tracker: when running inside the `\u002Fplan` workflow, also generate `docs\u002Fplans\u002Fwork\u002F{NNN}-{name}.md` per `.agents\u002Fworkflows\u002Fplan.md`\n- API contract template (SSOT): `..\u002F_shared\u002Fcore\u002Fapi-contracts\u002Ftemplate.md`; write generated contracts to `.agents\u002Fresults\u002Fapi-contracts\u002F` (run artifact) or `docs\u002Fplans\u002Fcontracts\u002F` (durable spec)\n- Context loading: `..\u002F_shared\u002Fcore\u002Fcontext-loading.md`\n- Reasoning templates: `..\u002F_shared\u002Fcore\u002Freasoning-templates.md`\n- Clarification: `..\u002F_shared\u002Fcore\u002Fclarification-protocol.md`\n- Context budget: `..\u002F_shared\u002Fcore\u002Fcontext-budget.md`\n- Lessons learned: `..\u002F_shared\u002Fcore\u002Flessons-learned.md`\n",{"name":5,"description":7},"main","ba5c378471d265938d6f5036c6b22c8e4a385c94",".agents\u002Fskills\u002Foma-pm",0,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader","https:\u002F\u002Fchromewebstore.google.com\u002Fdetail\u002Fkaltura-downloader\u002Fmmeomcgalmlhandhdgmfkjeaindgjhle","https:\u002F\u002Fgithub.com\u002Fgracefullight","https:\u002F\u002Fgracefullight.dev","I literally can’t sleep if I don’t code for even a single day.","2026-10-06 01:43:25",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add gracefullight\u002Fkaltura-downloader --skill oma-pm",{"tool":60,"command":61},"bunx","bunx skills add gracefullight\u002Fkaltura-downloader --skill oma-pm",{"tool":63,"command":64},"pnpm","pnpm dlx skills add gracefullight\u002Fkaltura-downloader --skill oma-pm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002FSKILL.md",true,[68,74,78,82,86,90],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"resources\u002Ferror-playbook.md","REFERENCE","参考文档",2787,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002Fresources\u002Ferror-playbook.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"resources\u002Fexamples.md",4633,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002Fresources\u002Fexamples.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"resources\u002Fexecution-protocol.md",3776,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002Fresources\u002Fexecution-protocol.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"resources\u002Fiso-planning.md",2547,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002Fresources\u002Fiso-planning.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"resources\u002Fplan-phase-protocol.md",1354,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002Fresources\u002Fplan-phase-protocol.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"resources\u002Ftask-template.json",1526,"https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Foma-pm\u002Fresources\u002Ftask-template.json",[95,101,113,119,126,135],{"skillNo":96,"name":97,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":39},"01M6J7W2SFEJKP2QSQBA68Q49X","work","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fwork\u002FSKILL.md",[],[97],{"skillNo":102,"name":103,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":39},"01M6J7W17HBR9RJHF63SAWTR3X","video","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fvideo\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[112],"Video",{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":39},"01M6J7VZMFE8WVH33K0DEPC2YR","ultrawork","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fultrawork\u002FSKILL.md",[],[115],{"skillNo":120,"name":121,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":39},"01M6J7VY165B9KNA578KWF8RQA","tools","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Ftools\u002FSKILL.md",[],[125],"Tools",{"skillNo":127,"name":128,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":39},"01M6J7VWBNB3JGJMYRRF7C764J","stack-set","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstack-set\u002FSKILL.md",[],[132,133,134],"SET","stack","stack set",{"skillNo":136,"name":137,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":39},"01M6J7VTSHG09PBTYRHQ7V8RX2","setup","https:\u002F\u002Fgithub.com\u002Fgracefullight\u002Fkaltura-downloader\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fsetup\u002FSKILL.md",[],[137]]