[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WPNZAVFNVYM8X3M1KB9KB":3,"skill-same:01M77WPNZAVFNVYM8X3M1KB9KB":56},{"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},"01M77WPNZAVFNVYM8X3M1KB9KB","team-composition-patterns",null,"Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring display modes (tmux, iTerm2, in-process) for a CI or local environment, or when building a custom team composition for a non-standard workflow such as a migration or security audit.","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\u002Fagent\u002Fskills\u002Fteam-composition-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring display modes (tmux, iTerm2, in-process) for a CI or local environment, or when building a custom team composition for a non-standard workflow such as a migration or security audit.\"\n---\n# Team Composition Patterns\n\nBest practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.\n\n## When to Use This Skill\n\n- Deciding how many teammates to spawn for a task\n- Choosing between preset team configurations\n- Selecting the right agent type (subagent_type) for each role\n- Configuring teammate display modes (tmux, iTerm2, in-process)\n- Building custom team compositions for non-standard workflows\n\n## Team Sizing Heuristics\n\n| Complexity   | Team Size | When to Use                                                 |\n| ------------ | --------- | ----------------------------------------------------------- |\n| Simple       | 1-2       | Single-dimension review, isolated bug, small feature        |\n| Moderate     | 2-3       | Multi-file changes, 2-3 concerns, medium features           |\n| Complex      | 3-4       | Cross-cutting concerns, large features, deep debugging      |\n| Very Complex | 4-5       | Full-stack features, comprehensive reviews, systemic issues |\n\n**Rule of thumb**: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.\n\n## Preset Team Compositions\n\n### Review Team\n\n- **Size**: 3 reviewers\n- **Agents**: 3x `team-reviewer`\n- **Default dimensions**: security, performance, architecture\n- **Use when**: Code changes need multi-dimensional quality assessment\n\n### Debug Team\n\n- **Size**: 3 investigators\n- **Agents**: 3x `team-debugger`\n- **Default hypotheses**: 3 competing hypotheses\n- **Use when**: Bug has multiple plausible root causes\n\n### Feature Team\n\n- **Size**: 3 (1 lead + 2 implementers)\n- **Agents**: 1x `team-lead` + 2x `team-implementer`\n- **Use when**: Feature can be decomposed into parallel work streams\n\n### Fullstack Team\n\n- **Size**: 4 (1 lead + 3 implementers)\n- **Agents**: 1x `team-lead` + 1x frontend `team-implementer` + 1x backend `team-implementer` + 1x test `team-implementer`\n- **Use when**: Feature spans frontend, backend, and test layers\n\n### Research Team\n\n- **Size**: 3 researchers\n- **Agents**: 3x `general-purpose`\n- **Default areas**: Each assigned a different research question, module, or topic\n- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch)\n- **Use when**: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel\n\n### Security Team\n\n- **Size**: 4 reviewers\n- **Agents**: 4x `team-reviewer`\n- **Default dimensions**: OWASP\u002Fvulnerabilities, auth\u002Faccess control, dependencies\u002Fsupply chain, secrets\u002Fconfiguration\n- **Use when**: Comprehensive security audit covering multiple attack surfaces\n\n### Migration Team\n\n- **Size**: 4 (1 lead + 2 implementers + 1 reviewer)\n- **Agents**: 1x `team-lead` + 2x `team-implementer` + 1x `team-reviewer`\n- **Use when**: Large codebase migration (framework upgrade, language port, API version bump) requiring parallel work with correctness verification\n\n## Agent Type Selection\n\nWhen spawning teammates with the `Agent` tool, choose `subagent_type` based on what tools the teammate needs:\n\n| Agent Type                     | Tools Available                                      | Use For                                                    |\n| ------------------------------ | ---------------------------------------------------- | ---------------------------------------------------------- |\n| `general-purpose`              | All tools (Read, Write, Edit, Bash, etc.)            | Implementation, debugging, any task requiring file changes |\n| `Explore`                      | Read-only tools (Read, Grep, Glob)                   | Research, code exploration, analysis                       |\n| `Plan`                         | Read-only tools                                      | Architecture planning, task decomposition                  |\n| `agent-teams:team-reviewer`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Code review with structured findings               |\n| `agent-teams:team-debugger`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Hypothesis-driven investigation                    |\n| `agent-teams:team-implementer` | Read\u002FWrite\u002FEdit\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Building features within file ownership boundaries |\n| `agent-teams:team-lead`        | Read\u002Fsearch\u002FBash plus Agent Teams coordination tools | Team orchestration and coordination                        |\n\n**Key distinction**: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.\n\n## Display Mode Configuration\n\nConfigure in `~\u002F.claude\u002Fsettings.json`:\n\n```json\n{\n  \"teammateMode\": \"tmux\"\n}\n```\n\n| Mode           | Behavior                       | Best For                                          |\n| -------------- | ------------------------------ | ------------------------------------------------- |\n| `\"tmux\"`       | Each teammate in a tmux pane   | Development workflows, monitoring multiple agents |\n| `\"iterm2\"`     | Each teammate in an iTerm2 tab | macOS users who prefer iTerm2                     |\n| `\"in-process\"` | All teammates in same process  | Simple tasks, CI\u002FCD environments                  |\n\n## Custom Team Guidelines\n\nWhen building custom teams:\n\n1. **Every team needs a coordinator** — Either designate a `team-lead` or have the user coordinate directly\n2. **Match roles to agent types** — Use specialized agents (reviewer, debugger, implementer) when available\n3. **Avoid duplicate roles** — Two agents doing the same thing wastes resources\n4. **Define boundaries upfront** — Each teammate needs clear ownership of files or responsibilities\n5. **Keep it small** — 2-4 teammates is the sweet spot; 5+ requires significant coordination overhead\n\n## Troubleshooting\n\n**A teammate was spawned as `Explore` but needs to write files.**\n`Explore` and `Plan` are read-only agents. Change the `subagent_type` to `general-purpose` or an appropriate specialized agent type. Never assign implementation tasks to read-only agents.\n\n**The team is growing too large and coordination is slowing everything down.**\nEach additional teammate adds communication overhead. Consolidate roles: can one agent cover two dimensions? A 4-person team doing 6 independent tasks is usually better served by 3 agents covering 2 tasks each.\n\n**tmux mode is not showing panes.**\nEnsure tmux is installed and a session is already running before spawning teammates. The `in-process` mode works without tmux and is suitable for CI or scripted environments.\n\n**Two reviewers are flagging the same issues.**\nThe review dimensions overlap. Redefine each reviewer's focus area: one on correctness\u002Flogic, one on security, one on performance\u002Fscalability. Overlapping coverage wastes tokens and produces duplicate findings.\n\n**A `team-lead` is spawning teammates but they are not receiving tasks.**\nVerify that the lead is using the `Agent` tool to spawn teammates and passing complete context in the prompt. Teammates start fresh with no prior conversation history — they need all relevant information in their initial prompt.\n\n## Related Skills\n\n- [parallel-feature-development](..\u002Fparallel-feature-development\u002FSKILL.md) — Decompose work streams and assign file ownership once the team is composed\n- [team-communication-protocols](..\u002Fteam-communication-protocols\u002FSKILL.md) — Establish messaging norms and shutdown procedures for the assembled team\n","# Team Composition Patterns\n\nBest practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.\n\n## When to Use This Skill\n\n- Deciding how many teammates to spawn for a task\n- Choosing between preset team configurations\n- Selecting the right agent type (subagent_type) for each role\n- Configuring teammate display modes (tmux, iTerm2, in-process)\n- Building custom team compositions for non-standard workflows\n\n## Team Sizing Heuristics\n\n| Complexity   | Team Size | When to Use                                                 |\n| ------------ | --------- | ----------------------------------------------------------- |\n| Simple       | 1-2       | Single-dimension review, isolated bug, small feature        |\n| Moderate     | 2-3       | Multi-file changes, 2-3 concerns, medium features           |\n| Complex      | 3-4       | Cross-cutting concerns, large features, deep debugging      |\n| Very Complex | 4-5       | Full-stack features, comprehensive reviews, systemic issues |\n\n**Rule of thumb**: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.\n\n## Preset Team Compositions\n\n### Review Team\n\n- **Size**: 3 reviewers\n- **Agents**: 3x `team-reviewer`\n- **Default dimensions**: security, performance, architecture\n- **Use when**: Code changes need multi-dimensional quality assessment\n\n### Debug Team\n\n- **Size**: 3 investigators\n- **Agents**: 3x `team-debugger`\n- **Default hypotheses**: 3 competing hypotheses\n- **Use when**: Bug has multiple plausible root causes\n\n### Feature Team\n\n- **Size**: 3 (1 lead + 2 implementers)\n- **Agents**: 1x `team-lead` + 2x `team-implementer`\n- **Use when**: Feature can be decomposed into parallel work streams\n\n### Fullstack Team\n\n- **Size**: 4 (1 lead + 3 implementers)\n- **Agents**: 1x `team-lead` + 1x frontend `team-implementer` + 1x backend `team-implementer` + 1x test `team-implementer`\n- **Use when**: Feature spans frontend, backend, and test layers\n\n### Research Team\n\n- **Size**: 3 researchers\n- **Agents**: 3x `general-purpose`\n- **Default areas**: Each assigned a different research question, module, or topic\n- **Capabilities**: Codebase search (Grep, Glob, Read), web search (WebSearch, WebFetch)\n- **Use when**: Need to understand a codebase, research libraries, compare approaches, or gather information from code and web sources in parallel\n\n### Security Team\n\n- **Size**: 4 reviewers\n- **Agents**: 4x `team-reviewer`\n- **Default dimensions**: OWASP\u002Fvulnerabilities, auth\u002Faccess control, dependencies\u002Fsupply chain, secrets\u002Fconfiguration\n- **Use when**: Comprehensive security audit covering multiple attack surfaces\n\n### Migration Team\n\n- **Size**: 4 (1 lead + 2 implementers + 1 reviewer)\n- **Agents**: 1x `team-lead` + 2x `team-implementer` + 1x `team-reviewer`\n- **Use when**: Large codebase migration (framework upgrade, language port, API version bump) requiring parallel work with correctness verification\n\n## Agent Type Selection\n\nWhen spawning teammates with the `Agent` tool, choose `subagent_type` based on what tools the teammate needs:\n\n| Agent Type                     | Tools Available                                      | Use For                                                    |\n| ------------------------------ | ---------------------------------------------------- | ---------------------------------------------------------- |\n| `general-purpose`              | All tools (Read, Write, Edit, Bash, etc.)            | Implementation, debugging, any task requiring file changes |\n| `Explore`                      | Read-only tools (Read, Grep, Glob)                   | Research, code exploration, analysis                       |\n| `Plan`                         | Read-only tools                                      | Architecture planning, task decomposition                  |\n| `agent-teams:team-reviewer`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Code review with structured findings               |\n| `agent-teams:team-debugger`    | Read\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Hypothesis-driven investigation                    |\n| `agent-teams:team-implementer` | Read\u002FWrite\u002FEdit\u002Fsearch\u002FBash plus TaskList\u002FTaskGet\u002FTaskUpdate\u002FSendMessage | Building features within file ownership boundaries |\n| `agent-teams:team-lead`        | Read\u002Fsearch\u002FBash plus Agent Teams coordination tools | Team orchestration and coordination                        |\n\n**Key distinction**: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.\n\n## Display Mode Configuration\n\nConfigure in `~\u002F.claude\u002Fsettings.json`:\n\n```json\n{\n  \"teammateMode\": \"tmux\"\n}\n```\n\n| Mode           | Behavior                       | Best For                                          |\n| -------------- | ------------------------------ | ------------------------------------------------- |\n| `\"tmux\"`       | Each teammate in a tmux pane   | Development workflows, monitoring multiple agents |\n| `\"iterm2\"`     | Each teammate in an iTerm2 tab | macOS users who prefer iTerm2                     |\n| `\"in-process\"` | All teammates in same process  | Simple tasks, CI\u002FCD environments                  |\n\n## Custom Team Guidelines\n\nWhen building custom teams:\n\n1. **Every team needs a coordinator** — Either designate a `team-lead` or have the user coordinate directly\n2. **Match roles to agent types** — Use specialized agents (reviewer, debugger, implementer) when available\n3. **Avoid duplicate roles** — Two agents doing the same thing wastes resources\n4. **Define boundaries upfront** — Each teammate needs clear ownership of files or responsibilities\n5. **Keep it small** — 2-4 teammates is the sweet spot; 5+ requires significant coordination overhead\n\n## Troubleshooting\n\n**A teammate was spawned as `Explore` but needs to write files.**\n`Explore` and `Plan` are read-only agents. Change the `subagent_type` to `general-purpose` or an appropriate specialized agent type. Never assign implementation tasks to read-only agents.\n\n**The team is growing too large and coordination is slowing everything down.**\nEach additional teammate adds communication overhead. Consolidate roles: can one agent cover two dimensions? A 4-person team doing 6 independent tasks is usually better served by 3 agents covering 2 tasks each.\n\n**tmux mode is not showing panes.**\nEnsure tmux is installed and a session is already running before spawning teammates. The `in-process` mode works without tmux and is suitable for CI or scripted environments.\n\n**Two reviewers are flagging the same issues.**\nThe review dimensions overlap. Redefine each reviewer's focus area: one on correctness\u002Flogic, one on security, one on performance\u002Fscalability. Overlapping coverage wastes tokens and produces duplicate findings.\n\n**A `team-lead` is spawning teammates but they are not receiving tasks.**\nVerify that the lead is using the `Agent` tool to spawn teammates and passing complete context in the prompt. Teammates start fresh with no prior conversation history — they need all relevant information in their initial prompt.\n\n## Related Skills\n\n- [parallel-feature-development](..\u002Fparallel-feature-development\u002FSKILL.md) — Decompose work streams and assign file ownership once the team is composed\n- [team-communication-protocols](..\u002Fteam-communication-protocols\u002FSKILL.md) — Establish messaging norms and shutdown procedures for the assembled team\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fteam-composition-patterns",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 team-composition-patterns",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill team-composition-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill team-composition-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fteam-composition-patterns\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fagent-type-selection.md","REFERENCE","参考文档",3546,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fteam-composition-patterns\u002Freferences\u002Fagent-type-selection.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fpreset-teams.md",9116,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fteam-composition-patterns\u002Freferences\u002Fpreset-teams.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]