[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVJ6BB81NTMHEZWS0MFY6X":3,"skill-same:01M7EVJ6BB81NTMHEZWS0MFY6X":57},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7EVJ6BB81NTMHEZWS0MFY6X","competitor-tracking",null,"Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fcompetitor-tracking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ncategory: development\nname: competitor-tracking\ndescription: \"Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fcompetitor-tracking\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Competitor Tracking\n## When to Use\n\nUse this skill when you need systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: \"competitor analysis\", \"track competitors\", \"competitive intelligence\", \"competitor research\", \"what...\n\n\nSystematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.\n\n## Overview\n\nCompetitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding\u002Ftrajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.\n\nEffective competitor tracking helps you:\n- Understand your competitive positioning\n- Anticipate competitor moves\n- Arm sales and marketing with accurate battlecards\n- Identify market gaps and opportunities\n- Learn from competitor successes and failures\n\n## Competitor Identification\n\n### Types of Competitors\n\n**Direct Competitors:**\n- Same category, same target developer\n- Solve the same core problem\n- Would appear in the same \"best X tools\" lists\n- Example: If you're a CI\u002FCD tool, other CI\u002FCD tools\n\n**Indirect Competitors:**\n- Adjacent categories that overlap with your use case\n- Might be expanding into your space\n- Developers might use instead of your category\n- Example: GitHub Actions competing with standalone CI tools\n\n**DIY Alternatives:**\n- Open source tools developers self-host\n- Custom scripts and internal tooling\n- \"Just use bash scripts\" or \"build it yourself\"\n- Often your biggest competitor by volume\n\n**Platform Alternatives:**\n- Cloud provider native services (AWS, GCP, Azure equivalents)\n- All-in-one platforms that include your functionality\n- Enterprise suite solutions\n\n### Competitive Landscape Mapping\n\nCreate a competitive landscape document with:\n\n1. **Competitor profiles** - Company, product, target market, positioning\n2. **Feature matrix** - Core features compared across competitors\n3. **Pricing comparison** - Tiers, pricing model, enterprise pricing signals\n4. **Strengths\u002Fweaknesses** - Honest assessment of each competitor\n5. **Trajectory** - Funding, growth signals, strategic direction\n\n## What to Track\n\n### Product and Features\n\n**Track weekly\u002Fmonthly:**\n- Changelog and release notes\n- New feature announcements\n- Pricing changes\n- Integration announcements\n- API changes\n- SDK\u002Flibrary updates\n\n**How to track:**\n- Subscribe to competitor newsletters\n- Follow their GitHub releases\n- Monitor their Twitter\u002Fblog\n- Set up monitoring alerts for \"[competitor] launch\" \"[competitor] announces\"\n\n### Pricing and Packaging\n\n**Key signals:**\n- Pricing page changes (use archive.org to track history)\n- New tier introductions\n- Enterprise\u002Fcustom pricing signals\n- Free tier changes\n- Usage-based vs seat-based shifts\n\n**Competitive pricing intelligence:**\n- What's included in free tier?\n- Where are the upgrade triggers?\n- How do they handle overages?\n- What's the enterprise motion?\n\n### Positioning and Messaging\n\n**Track changes in:**\n- Homepage headline and hero\n- \"Who it's for\" positioning\n- Primary use cases emphasized\n- Comparison pages (how they position against others)\n- Case studies and social proof\n\n**Analyze:**\n- What problem do they lead with?\n- What audience are they targeting?\n- What's their unique angle?\n- How are they different from 6 months ago?\n\n### Content Strategy\n\n**Monitor:**\n- Blog post frequency and topics\n- Documentation quality and coverage\n- Video\u002Ftutorial content\n- Conference talks and sponsorships\n- Developer education initiatives\n\n**Look for:**\n- SEO plays (what keywords are they targeting?)\n- Content gaps you can exploit\n- Successful content formats to learn from\n\n### Community and Traction\n\n**GitHub signals:**\n- Stars\u002Fforks growth rate\n- Issue volume and response time\n- Contributor growth\n- Release frequency\n\n**Community signals:**\n- Discord\u002FSlack member counts\n- Forum activity\n- Stack Overflow tag activity\n- Reddit mention frequency\n\n## Developer Sentiment Monitoring\n\n### Setting Up Competitor Monitoring\n\nUse social listening tools to track developer sentiment toward competitors across platforms. Set up alerts for:\n\n- Competitor brand mentions\n- Negative sentiment toward competitors (opportunity signals)\n- Comparison queries (\"[competitor] vs\")\n\n### Key Sentiment Signals\n\n**Churn signals:**\n- \"Migrating away from [competitor]\"\n- \"Looking for [competitor] alternative\"\n- \"Frustrated with [competitor]\"\n- \"Canceling [competitor]\"\n\n**Praise signals (learn from them):**\n- \"Love [competitor]'s [feature]\"\n- \"[Competitor] just works\"\n- \"Best part of [competitor] is...\"\n\n**Feature gaps:**\n- \"Wish [competitor] had...\"\n- \"[Competitor] doesn't support...\"\n- \"Waiting for [competitor] to add...\"\n\n### Competitive Sentiment Analysis\n\nUse your monitoring tool's analytics for trend analysis:\n\n- Mention volume for competitors over 90 days\n- Sentiment distribution: positive vs negative\n- Co-mentions where competitor and your brand appear together\n\n## Building Competitive Battlecards\n\n### Battlecard Structure\n\nCreate battlecards for sales and marketing teams:\n\n**1. Competitor Overview**\n- Company background\n- Target market\n- Key value proposition\n- Recent news\u002Ftrajectory\n\n**2. When We Win**\n- Scenarios where you have advantage\n- Customer types that prefer you\n- Use cases you excel at\n- Proof points and case studies\n\n**3. When We Lose**\n- Scenarios where competitor has advantage\n- What to watch out for\n- How to mitigate their strengths\n\n**4. Common Objections**\n- \"But [competitor] has [feature]\"\n- \"[Competitor] is cheaper\"\n- \"[Competitor] is more established\"\n- Response frameworks for each\n\n**5. Competitive Differentiation**\n- Key technical differences\n- Pricing comparison\n- Support\u002Fservice differences\n- Community\u002Fecosystem differences\n\n**6. Landmines to Set**\n- Questions to ask that favor you\n- Requirements that highlight your strengths\n- Evaluation criteria that matter\n\n### Keeping Battlecards Fresh\n\n**Update triggers:**\n- Competitor launches major feature\n- Competitor changes pricing\n- You ship something that changes the comparison\n- Sales team reports new objections\n- Win\u002Floss analysis reveals new patterns\n\n**Review cadence:**\n- Major competitors: monthly review\n- Minor competitors: quarterly review\n- Emerging competitors: as needed\n\n## Responding to Competitor Moves\n\n### When to Respond\n\n**Always respond:**\n- Competitor makes false claims about you\n- Competitor targets your specific customers\n- Major market shift that affects positioning\n\n**Consider responding:**\n- Competitor launches feature you have\n- Competitor enters your core market\n- Competitor's crisis creates opportunity\n\n**Usually don't respond:**\n- Minor feature parity announcements\n- Competitor's internal issues (unless affects their customers)\n- Petty competitive shots\n\n### Response Playbooks\n\n**Feature launch response:**\n1. Assess: Do we have parity? Better? Gap?\n2. Internal communication to sales\u002Fsupport\n3. Update battlecards if needed\n4. Consider content response (blog, comparison page update)\n5. Monitor developer conversations for context\n\n**Pricing change response:**\n1. Analyze impact on competitive positioning\n2. Update pricing comparison materials\n3. Brief sales team\n4. Consider if pricing adjustment needed\n5. Monitor churn\u002Facquisition impact\n\n**Crisis opportunity response:**\n1. Don't be sleazy or pile on\n2. Be helpful to affected users if appropriate\n3. Create migration content if there's genuine demand\n4. Let your product speak for itself\n\n## Tools\n\n### Social Listening\n\nUse monitoring tools to set up alerts for these patterns:\n- Competitor sentiment overview (last 30 days, by sentiment)\n- Churn signals: \"alternative OR migrating OR switching\" + competitor name\n- Feature gaps: \"wish OR need OR missing\" + competitor name\n- Comparison mentions: \"[competitor] vs\"\n\n### Other Tools\n\n**GitHub Monitoring:**\n```bash\n# Track competitor repo activity\ngh api repos\u002F[competitor]\u002F[repo] --jq '.stargazers_count, .open_issues_count'\n\n# Search for competitor mentions in issues\ngh search issues \"[competitor]\" --limit 50\n```\n\n**npm\u002FPyPI Monitoring:**\n- Track download trends for competitor packages\n- Monitor version release frequency\n- Watch for new packages in their ecosystem\n\n**Archive.org:**\n- Track historical changes to competitor websites\n- Document pricing changes over time\n- Capture positioning shifts\n\n**LinkedIn\u002FCareers:**\n- Track hiring patterns\n- Identify strategic direction from job postings\n- Monitor team growth signals\n\n## Related Skills\n\n- **developer-listening** - Broader monitoring beyond just competitors\n- **alternatives-pages** - Turn competitive intelligence into content\n- **positioning** - Differentiate based on competitive insights\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Competitor Tracking\n## When to Use\n\nUse this skill when you need systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: \"competitor analysis\", \"track competitors\", \"competitive intelligence\", \"competitor research\", \"what...\n\n\nSystematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.\n\n## Overview\n\nCompetitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding\u002Ftrajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.\n\nEffective competitor tracking helps you:\n- Understand your competitive positioning\n- Anticipate competitor moves\n- Arm sales and marketing with accurate battlecards\n- Identify market gaps and opportunities\n- Learn from competitor successes and failures\n\n## Competitor Identification\n\n### Types of Competitors\n\n**Direct Competitors:**\n- Same category, same target developer\n- Solve the same core problem\n- Would appear in the same \"best X tools\" lists\n- Example: If you're a CI\u002FCD tool, other CI\u002FCD tools\n\n**Indirect Competitors:**\n- Adjacent categories that overlap with your use case\n- Might be expanding into your space\n- Developers might use instead of your category\n- Example: GitHub Actions competing with standalone CI tools\n\n**DIY Alternatives:**\n- Open source tools developers self-host\n- Custom scripts and internal tooling\n- \"Just use bash scripts\" or \"build it yourself\"\n- Often your biggest competitor by volume\n\n**Platform Alternatives:**\n- Cloud provider native services (AWS, GCP, Azure equivalents)\n- All-in-one platforms that include your functionality\n- Enterprise suite solutions\n\n### Competitive Landscape Mapping\n\nCreate a competitive landscape document with:\n\n1. **Competitor profiles** - Company, product, target market, positioning\n2. **Feature matrix** - Core features compared across competitors\n3. **Pricing comparison** - Tiers, pricing model, enterprise pricing signals\n4. **Strengths\u002Fweaknesses** - Honest assessment of each competitor\n5. **Trajectory** - Funding, growth signals, strategic direction\n\n## What to Track\n\n### Product and Features\n\n**Track weekly\u002Fmonthly:**\n- Changelog and release notes\n- New feature announcements\n- Pricing changes\n- Integration announcements\n- API changes\n- SDK\u002Flibrary updates\n\n**How to track:**\n- Subscribe to competitor newsletters\n- Follow their GitHub releases\n- Monitor their Twitter\u002Fblog\n- Set up monitoring alerts for \"[competitor] launch\" \"[competitor] announces\"\n\n### Pricing and Packaging\n\n**Key signals:**\n- Pricing page changes (use archive.org to track history)\n- New tier introductions\n- Enterprise\u002Fcustom pricing signals\n- Free tier changes\n- Usage-based vs seat-based shifts\n\n**Competitive pricing intelligence:**\n- What's included in free tier?\n- Where are the upgrade triggers?\n- How do they handle overages?\n- What's the enterprise motion?\n\n### Positioning and Messaging\n\n**Track changes in:**\n- Homepage headline and hero\n- \"Who it's for\" positioning\n- Primary use cases emphasized\n- Comparison pages (how they position against others)\n- Case studies and social proof\n\n**Analyze:**\n- What problem do they lead with?\n- What audience are they targeting?\n- What's their unique angle?\n- How are they different from 6 months ago?\n\n### Content Strategy\n\n**Monitor:**\n- Blog post frequency and topics\n- Documentation quality and coverage\n- Video\u002Ftutorial content\n- Conference talks and sponsorships\n- Developer education initiatives\n\n**Look for:**\n- SEO plays (what keywords are they targeting?)\n- Content gaps you can exploit\n- Successful content formats to learn from\n\n### Community and Traction\n\n**GitHub signals:**\n- Stars\u002Fforks growth rate\n- Issue volume and response time\n- Contributor growth\n- Release frequency\n\n**Community signals:**\n- Discord\u002FSlack member counts\n- Forum activity\n- Stack Overflow tag activity\n- Reddit mention frequency\n\n## Developer Sentiment Monitoring\n\n### Setting Up Competitor Monitoring\n\nUse social listening tools to track developer sentiment toward competitors across platforms. Set up alerts for:\n\n- Competitor brand mentions\n- Negative sentiment toward competitors (opportunity signals)\n- Comparison queries (\"[competitor] vs\")\n\n### Key Sentiment Signals\n\n**Churn signals:**\n- \"Migrating away from [competitor]\"\n- \"Looking for [competitor] alternative\"\n- \"Frustrated with [competitor]\"\n- \"Canceling [competitor]\"\n\n**Praise signals (learn from them):**\n- \"Love [competitor]'s [feature]\"\n- \"[Competitor] just works\"\n- \"Best part of [competitor] is...\"\n\n**Feature gaps:**\n- \"Wish [competitor] had...\"\n- \"[Competitor] doesn't support...\"\n- \"Waiting for [competitor] to add...\"\n\n### Competitive Sentiment Analysis\n\nUse your monitoring tool's analytics for trend analysis:\n\n- Mention volume for competitors over 90 days\n- Sentiment distribution: positive vs negative\n- Co-mentions where competitor and your brand appear together\n\n## Building Competitive Battlecards\n\n### Battlecard Structure\n\nCreate battlecards for sales and marketing teams:\n\n**1. Competitor Overview**\n- Company background\n- Target market\n- Key value proposition\n- Recent news\u002Ftrajectory\n\n**2. When We Win**\n- Scenarios where you have advantage\n- Customer types that prefer you\n- Use cases you excel at\n- Proof points and case studies\n\n**3. When We Lose**\n- Scenarios where competitor has advantage\n- What to watch out for\n- How to mitigate their strengths\n\n**4. Common Objections**\n- \"But [competitor] has [feature]\"\n- \"[Competitor] is cheaper\"\n- \"[Competitor] is more established\"\n- Response frameworks for each\n\n**5. Competitive Differentiation**\n- Key technical differences\n- Pricing comparison\n- Support\u002Fservice differences\n- Community\u002Fecosystem differences\n\n**6. Landmines to Set**\n- Questions to ask that favor you\n- Requirements that highlight your strengths\n- Evaluation criteria that matter\n\n### Keeping Battlecards Fresh\n\n**Update triggers:**\n- Competitor launches major feature\n- Competitor changes pricing\n- You ship something that changes the comparison\n- Sales team reports new objections\n- Win\u002Floss analysis reveals new patterns\n\n**Review cadence:**\n- Major competitors: monthly review\n- Minor competitors: quarterly review\n- Emerging competitors: as needed\n\n## Responding to Competitor Moves\n\n### When to Respond\n\n**Always respond:**\n- Competitor makes false claims about you\n- Competitor targets your specific customers\n- Major market shift that affects positioning\n\n**Consider responding:**\n- Competitor launches feature you have\n- Competitor enters your core market\n- Competitor's crisis creates opportunity\n\n**Usually don't respond:**\n- Minor feature parity announcements\n- Competitor's internal issues (unless affects their customers)\n- Petty competitive shots\n\n### Response Playbooks\n\n**Feature launch response:**\n1. Assess: Do we have parity? Better? Gap?\n2. Internal communication to sales\u002Fsupport\n3. Update battlecards if needed\n4. Consider content response (blog, comparison page update)\n5. Monitor developer conversations for context\n\n**Pricing change response:**\n1. Analyze impact on competitive positioning\n2. Update pricing comparison materials\n3. Brief sales team\n4. Consider if pricing adjustment needed\n5. Monitor churn\u002Facquisition impact\n\n**Crisis opportunity response:**\n1. Don't be sleazy or pile on\n2. Be helpful to affected users if appropriate\n3. Create migration content if there's genuine demand\n4. Let your product speak for itself\n\n## Tools\n\n### Social Listening\n\nUse monitoring tools to set up alerts for these patterns:\n- Competitor sentiment overview (last 30 days, by sentiment)\n- Churn signals: \"alternative OR migrating OR switching\" + competitor name\n- Feature gaps: \"wish OR need OR missing\" + competitor name\n- Comparison mentions: \"[competitor] vs\"\n\n### Other Tools\n\n**GitHub Monitoring:**\n```bash\n# Track competitor repo activity\ngh api repos\u002F[competitor]\u002F[repo] --jq '.stargazers_count, .open_issues_count'\n\n# Search for competitor mentions in issues\ngh search issues \"[competitor]\" --limit 50\n```\n\n**npm\u002FPyPI Monitoring:**\n- Track download trends for competitor packages\n- Monitor version release frequency\n- Watch for new packages in their ecosystem\n\n**Archive.org:**\n- Track historical changes to competitor websites\n- Document pricing changes over time\n- Capture positioning shifts\n\n**LinkedIn\u002FCareers:**\n- Track hiring patterns\n- Identify strategic direction from job postings\n- Monitor team growth signals\n\n## Related Skills\n\n- **developer-listening** - Broader monitoring beyond just competitors\n- **alternatives-pages** - Turn competitive intelligence into content\n- **positioning** - Differentiate based on competitive insights\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"category":26,"date_added":27,"description":7,"source_repo":28,"source_type":29,"license_source":30},"critical","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fcompetitor-tracking","development",1782864000000,"jonathimer\u002Fdevmarketing-skills","community","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fdevelopment\u002Fcompetitor-tracking","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill competitor-tracking",{"tool":43,"command":44},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill competitor-tracking",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill competitor-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fcompetitor-tracking\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1353,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevelopment\u002Fcompetitor-tracking\u002FREADME.md",[58,66,73,80,87,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":65},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":65},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":65},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":65},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"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":65},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]