AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 22,822
- リポジトリ
- 3519
- 最終同期
- 2026/11/02
sambertechnical-video-script
Writes or reviews a shooting-ready script for a technical video or screencast - a two-column visual/narration beat sheet with a 30-second hook, code-on-screen pacing, chapters, a runtime budget, accessible narration, a cut list and a YouTube description with one CTA. Also storyboards 2-5 minute animated or motion design explainers. Use whenever someone mentions a screencast script, a demo or walkthrough video, a video tutorial script, a YouTube Shorts, TikTok or Reels script, an animated explain
- 24時間の導入数
- 432
- GitHub Stars
- 6
- 更新日
- 10月26日
samberdevrel-radar
Builds a personalised, time-budgeted watch list of developer-relations information sources - DevRel podcasts, newsletters, practice hubs, peer communities, conference calendars, ecosystem data reports and practitioners worth following - plus the routine that keeps it verified and fresh. Use whenever a developer advocate, community manager, DevRel lead or OSS maintainer asks for a DevRel radar, how to stay current on developer relations, which DevRel podcasts, newsletters or Slack communities des
- 24時間の導入数
- 431
- GitHub Stars
- 6
- 更新日
- 10月26日
samberdeveloper-community-launch
Decides whether, where and when to launch a developer community, then plans its seeding and first 90 days - venue selection, founding-member seeding, go/no-go criteria, the cheaper no-community alternatives, and shutdown criteria. Use whenever someone asks whether to start a Discord, Slack or forum for their users, which community platform to pick, how to launch or seed a developer community from zero, or how to reach critical mass - even if they only say "we should have a Discord". Do NOT use f
- 24時間の導入数
- 429
- GitHub Stars
- 6
- 更新日
- 10月26日
samberdevrel-hiring
Employer-side DevRel hiring - writes the job posting and outcome-based scorecard, designs the interview loop and question bank across the field's formats (presentation round, take-homes, DevRel-opinion round), scores a portfolio against the six-signal rubric, designs a paid work sample instead of unpaid spec work, and builds a 30-60-90 ramp anchored on a friction log. Splits by company type and funding driver. Use when the user asks how to hire a developer advocate, write a DevRel job posting, d
- 24時間の導入数
- 428
- GitHub Stars
- 6
- 更新日
- 10月26日
sambeross-distribution-strategy
Designs an open-source project's ongoing distribution mix after the launch window - registry metadata, code-host discovery surfaces, curated lists, downstream packaging, extension and connector marketplaces, the release stream, dependency-graph position, creator seeding, and procurement trust signals - ranked against real maintainer capacity. Use whenever a maintainer asks how people will keep finding the project, which registries or awesome lists to target, why adoption flattened after launch,
- 24時間の導入数
- 427
- GitHub Stars
- 6
- 更新日
- 10月26日
samberdevrel-strategy
Designs a company's developer relations program from the top - the business driver that funds it, the two goals it is allowed to serve, the pillar mix (advocacy, marketing, enablement, community) for its stage, audience priority, build-vs-buy per bet, staffing sequence, and a written refused list. Use whenever someone asks whether to start doing DevRel, what a new devrel program should do first, why devrel work is busy but not landing, how to justify the program to an exec, which pillar deserves
- 24時間の導入数
- 426
- GitHub Stars
- 6
- 更新日
- 10月26日
samberdeveloper-meetup-program
Designs and runs a recurring developer meetup or user group - purpose and host model, format menu, cadence, a standing speaker pipeline, in-kind venue and food sponsors with their conduct limits, no-show planning, the attendee-to-co-organizer ladder, and a health scorecard. Use whenever someone mentions starting a developer meetup or user group, dying meetup attendance, finding meetup speakers, getting a venue or pizza sponsor, how often to meet, RSVPs who never show, or handing the meetup over
- 24時間の導入数
- 426
- GitHub Stars
- 6
- 更新日
- 10月26日
morlutoreverse-engineer-anything
Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.
- 24時間の導入数
- 425
- GitHub Stars
- 41.9万
- 更新日
- 11月2日
samberdeveloper-ecosystem-strategy
Decides whether, when and how far a developer product should open into a platform other companies build on - extension points, partner-built integrations, third-party apps, a complement ecosystem - and what that permanently obliges you to. Use whenever someone asks if the product should become a platform, whether to open extension points or an app model to third parties, how to start an integration ecosystem, why nobody builds on the API, whether partners should build the connectors, or how much
- 24時間の導入数
- 425
- GitHub Stars
- 6
- 更新日
- 10月31日
samberdevrel-career
Plans, lands and advances a developer relations career from the candidate side - developer advocate, developer evangelist, DevRel engineer, community manager, developer educator, DX engineer. Covers portfolio audits against real hiring signals, a zero-to-hireable artefact curriculum, the six-rung IC ladder, the interview formats DevRel loops use (talk round, content and coding take-homes, DevRel-opinion round), gatekeeper and pit-trap patterns in postings, and offer evaluation weighing reporting
- 24時間の導入数
- 425
- GitHub Stars
- 6
- 更新日
- 10月26日
sambeross-launch
Plans and runs an open-source project launch end to end - name and license clearance, the readiness gate, positioning and one-liner, channel sequencing, the launch-day war room, star-velocity and GitHub Trending mechanics, and post-launch measurement. Use whenever someone is about to release, announce, open-source or "Show HN" a repository, asks how to reach GitHub Trending, wants the first real users or stars for a new library, is planning a Product Hunt post or a multi-day launch week, or asks
- 24時間の導入数
- 424
- GitHub Stars
- 6
- 更新日
- 10月26日
coreyhaines31influencer-marketing
When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and vetting partners, structuring deals, briefing creators, disclosure compliance, and measuring ROI. Also use when the user mentions 'influencer marketing,' 'creator partnerships,' 'sponsorships,' 'YouTube sponsorships,' 'podcast sponsorships,' 'newsletter sponsorship,' 'newsletter ad,' 'sponsor a newsletter,' 'brand ambassador,' 'ambassador program,' 'creator program,' 'UGC creators,'
- 24時間の導入数
- 412
- GitHub Stars
- 5.8万
- 更新日
- 10月31日
coreyhaines31reverse-engineer-marketing
When the user wants to reverse engineer how another company grew and copy what worked. Also use when the user mentions 'reverse engineer,' 'how did X grow,' 'how does X get customers,' 'growth teardown,' 'marketing teardown,' 'GTM teardown,' 'growth blueprint,' 'what is X doing for marketing,' 'what made X take off,' 'copy X's playbook,' 'X's distribution strategy,' 'what content works for X,' 'funnel hack,' 'map their funnel,' or 'watch what X is doing.' Builds a dated log of a company's moves
- 24時間の導入数
- 409
- GitHub Stars
- 5.8万
- 更新日
- 10月31日
coreyhaines31public-relations
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'press,' 'press release,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'reporter request,' 'tech press,' 'TechCrunch,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'p
- 24時間の導入数
- 408
- GitHub Stars
- 5.8万
- 更新日
- 10月31日
riekeltmulti-agent-review
Use when a spec or plan needs review before execution begins - "review my spec", "is this plan ready to execute", "check this before I build it", "second opinion on this plan" - and specifically before writing-plans (spec mode) or before subagent-driven-development (plan mode). Reviews specs and plans, not code. Panels six reviewers across two model tiers and three topics, invokes a reasoning-tier juror only when the tiers disagree, and gates the next workflow step with a fail-closed Blockers /
- 24時間の導入数
- 406
- GitHub Stars
- 82
- 更新日
- 8月22日
coreyhaines31link-building
When the user wants to earn backlinks or third-party mentions that lift rankings and AI citations. Also use when the user mentions 'link building,' 'linkbuilding,' 'backlinks,' 'get more backlinks,' 'link prospecting,' 'link gap,' 'competitor backlinks,' 'unlinked mentions,' 'link reclamation,' 'broken link building,' 'resource pages,' 'guest posting,' 'get into best-of lists,' 'listicle outreach,' 'domain rating,' 'referring domains,' 'anchor text,' or 'is this link vendor safe.' Use this whene
- 24時間の導入数
- 405
- GitHub Stars
- 5.8万
- 更新日
- 10月31日
coreyhaines31marketing-council
When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing m
- 24時間の導入数
- 405
- GitHub Stars
- 5.8万
- 更新日
- 10月31日
blockmaticw-api-docs
Refresh API docs from the owning schema source; never edit generated OpenAPI by hand.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日
blockmaticw-api-test
Add API tests that exercise public HTTP behavior against existing harnesses.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日
blockmaticw-build
Implement an agreed task incrementally and verify the result.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日
blockmaticw-clarify
Resolve consequential missing requirements from inspected context.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日
blockmaticw-coderabbit
Fetch CodeRabbit review comments, apply authorized fixes, and stop at local verification.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日
blockmaticw-comments
Process reviewer feedback, apply required fixes, and draft replies without unsolicited commits.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日
blockmaticw-commit
Review and commit the task's intended changes using repository conventions.
- 24時間の導入数
- 405
- GitHub Stars
- 1
- 更新日
- 9月20日