[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KQQFDMKSG2EKMKCABPCPF":3,"skill-same:01M77KQQFDMKSG2EKMKCABPCPF":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77KQQFDMKSG2EKMKCABPCPF","ai-team-orchestration",null,"Bootstrap and run a lightweight multi-agent development team. Use when starting or adopting a project, planning work, coordinating implementation and optional QA, brainstorming with distinct perspectives, or preserving context across sessions.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fai-team-orchestration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ai-team-orchestration\ndescription: 'Bootstrap and run a lightweight multi-agent development team. Use when starting or adopting a project, planning work, coordinating implementation and optional QA, brainstorming with distinct perspectives, or preserving context across sessions.'\n---\n\n# AI Team Orchestration\n\nUse three stable agents:\n\n| Agent | Purpose |\n|---|---|\n| `@ai-team-producer` | Clarify scope, plan proportionately, coordinate, and merge |\n| `@ai-team-dev` | Implement, test, self-review, and prepare the pull request |\n| `@ai-team-qa` | Independently test behavior when dedicated QA is useful |\n\nNova, Sage, and Milo are perspectives inside the Dev agent, not mandatory project layers.\n\n## Default Workflow\n\n**Plan -> Implement -> Test -> optional review or QA -> Merge -> update project state**\n\nKeep the workflow proportional:\n\n- Skip formal planning for small, obvious changes.\n- Use a short plan for multi-step or cross-cutting work.\n- Add independent review or QA when risk, uncertainty, or repository policy justifies it.\n- Let branch protection, required checks, permissions, and merge queues enforce repository merge policy.\n\n## Start or Adopt a Project\n\n1. Read existing repository instructions and documentation.\n2. Discover the actual stack, architecture, commands, deployment model, and risks.\n3. Create or update `PROJECT_BRIEF.md` only when durable cross-session context is useful. Start from the [project brief template](.\u002Freferences\u002Fproject-brief-template.md) and omit irrelevant sections.\n4. For substantial work, create a concise plan from the [sprint plan template](.\u002Freferences\u002Fsprint-plan-template.md).\n5. Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.\n\n## Execute\n\n### Producer\n\n- Define the outcome, constraints, acceptance criteria, and explicit exclusions.\n- Choose review and QA based on risk rather than ceremony.\n- Keep durable project state concise and current.\n\n### Dev\n\n- Follow repository conventions and implement the smallest complete solution.\n- Run relevant checks and inspect the final diff.\n- Open or update the pull request with summary, verification, and limitations.\n\n### QA\n\n- Use only when dedicated behavioral verification adds value.\n- Test the requested change and important regressions.\n- Report reproducible findings and verify fixes.\n\n## Brainstorms\n\nUse the [brainstorm format](.\u002Freferences\u002Fbrainstorm-format.md) for product or architecture decisions that benefit from competing perspectives. For ordinary implementation choices, let Dev decide using repository conventions.\n\n## Context Recovery\n\nBefore ending a long or interrupted session:\n\n1. Update the active plan or progress note if one exists.\n2. Record material decisions, blockers, and the next action in repository context.\n3. Use a cold-start prompt such as:\n\n```text\nRead the repository instructions, then read whichever sources exist for this\nwork: the active issue or request, PROJECT_BRIEF.md, and the active plan or\nprogress note.\nContinue from the recorded next action.\n```\n\n## Tool and Model Inheritance\n\nThe bundled agents intentionally omit `tools` and `model` frontmatter:\n\n- available built-in, MCP, and extension tools remain usable;\n- developers keep control of model selection;\n- role boundaries are defined by instructions and normal trust, permission, authentication, and approval controls.\n\nIf the environment exposes too many tools, deselect irrelevant tools or MCP servers, or use VS Code virtual-tool management. Do not add a machine-specific plugin allowlist.\n\n## Principles\n\n- Prefer working software and clear handoffs over process artifacts.\n- Follow repository policy instead of embedding universal Git commands.\n- Preserve unknown work and ask before destructive or privileged actions.\n- Keep bugs and important decisions in durable project systems, not only chat.\n- See [anti-patterns](.\u002Freferences\u002Fanti-patterns.md) for concise lessons.\n","# AI Team Orchestration\n\nUse three stable agents:\n\n| Agent | Purpose |\n|---|---|\n| `@ai-team-producer` | Clarify scope, plan proportionately, coordinate, and merge |\n| `@ai-team-dev` | Implement, test, self-review, and prepare the pull request |\n| `@ai-team-qa` | Independently test behavior when dedicated QA is useful |\n\nNova, Sage, and Milo are perspectives inside the Dev agent, not mandatory project layers.\n\n## Default Workflow\n\n**Plan -> Implement -> Test -> optional review or QA -> Merge -> update project state**\n\nKeep the workflow proportional:\n\n- Skip formal planning for small, obvious changes.\n- Use a short plan for multi-step or cross-cutting work.\n- Add independent review or QA when risk, uncertainty, or repository policy justifies it.\n- Let branch protection, required checks, permissions, and merge queues enforce repository merge policy.\n\n## Start or Adopt a Project\n\n1. Read existing repository instructions and documentation.\n2. Discover the actual stack, architecture, commands, deployment model, and risks.\n3. Create or update `PROJECT_BRIEF.md` only when durable cross-session context is useful. Start from the [project brief template](.\u002Freferences\u002Fproject-brief-template.md) and omit irrelevant sections.\n4. For substantial work, create a concise plan from the [sprint plan template](.\u002Freferences\u002Fsprint-plan-template.md).\n5. Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.\n\n## Execute\n\n### Producer\n\n- Define the outcome, constraints, acceptance criteria, and explicit exclusions.\n- Choose review and QA based on risk rather than ceremony.\n- Keep durable project state concise and current.\n\n### Dev\n\n- Follow repository conventions and implement the smallest complete solution.\n- Run relevant checks and inspect the final diff.\n- Open or update the pull request with summary, verification, and limitations.\n\n### QA\n\n- Use only when dedicated behavioral verification adds value.\n- Test the requested change and important regressions.\n- Report reproducible findings and verify fixes.\n\n## Brainstorms\n\nUse the [brainstorm format](.\u002Freferences\u002Fbrainstorm-format.md) for product or architecture decisions that benefit from competing perspectives. For ordinary implementation choices, let Dev decide using repository conventions.\n\n## Context Recovery\n\nBefore ending a long or interrupted session:\n\n1. Update the active plan or progress note if one exists.\n2. Record material decisions, blockers, and the next action in repository context.\n3. Use a cold-start prompt such as:\n\n```text\nRead the repository instructions, then read whichever sources exist for this\nwork: the active issue or request, PROJECT_BRIEF.md, and the active plan or\nprogress note.\nContinue from the recorded next action.\n```\n\n## Tool and Model Inheritance\n\nThe bundled agents intentionally omit `tools` and `model` frontmatter:\n\n- available built-in, MCP, and extension tools remain usable;\n- developers keep control of model selection;\n- role boundaries are defined by instructions and normal trust, permission, authentication, and approval controls.\n\nIf the environment exposes too many tools, deselect irrelevant tools or MCP servers, or use VS Code virtual-tool management. Do not add a machine-specific plugin allowlist.\n\n## Principles\n\n- Prefer working software and clear handoffs over process artifacts.\n- Follow repository policy instead of embedding universal Git commands.\n- Preserve unknown work and ask before destructive or privileged actions.\n- Keep bugs and important decisions in durable project systems, not only chat.\n- See [anti-patterns](.\u002Freferences\u002Fanti-patterns.md) for concise lessons.\n",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fai-team-orchestration",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill ai-team-orchestration",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill ai-team-orchestration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill ai-team-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fai-team-orchestration\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fanti-patterns.md","REFERENCE","参考文档",1539,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fai-team-orchestration\u002Freferences\u002Fanti-patterns.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fbrainstorm-format.md",3386,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fai-team-orchestration\u002Freferences\u002Fbrainstorm-format.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fproject-brief-template.md",1540,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fai-team-orchestration\u002Freferences\u002Fproject-brief-template.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fsprint-plan-template.md",1438,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fai-team-orchestration\u002Freferences\u002Fsprint-plan-template.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"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":106,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]