[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73FZ93C3H5DDFBMFMF06H80":3,"skill-same:01M73FZ93C3H5DDFBMFMF06H80":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":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M73FZ93C3H5DDFBMFMF06H80","competitor-monitoring",null,"When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions \"track competitors\", \"what are competitors doing\", \"competitor alerts\", or \"market watch\".","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fstartup--competitor-monitoring\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: competitor-monitoring\ndescription: When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions \"track competitors\", \"what are competitors doing\", \"competitor alerts\", or \"market watch\".\nrelated: [competitive-analysis, daily-product-digest, review-mining, market-research]\nreads: [startup-context]\norigin: \"startup\"\n---\n\n# Competitor Monitoring\n\n## When to Use\n- Founder wants to know when competitors change pricing, ship features, or raise funding\n- Founder wants a recurring \"what changed this week\" scan of competitor activity\n- Founder wants to detect strategic shifts from competitor job postings, blog posts, or product updates\n- Founder wants to stay informed without manually checking 10 websites daily\n\nThis is the **recurring sibling** of `competitive-analysis` (one-time deep dive). Use this skill for ongoing monitoring, not initial research.\n\n## Context Required\n- List of 3-7 competitors to track (names, websites, product URLs)\n- What the founder cares about most (pricing, features, positioning, hiring, funding, content)\n- Monitoring frequency (weekly recommended for early-stage, biweekly for established markets)\n- The founder's own positioning (to flag threats and opportunities)\n\n## Workflow\n\n1. **Define the monitoring surface** — for each competitor, identify what to watch:\n   - **Pricing page** — plan changes, new tiers, free plan adjustments\n   - **Changelog \u002F release notes** — new features, deprecations, platform shifts\n   - **Job postings** — engineering roles signal product direction, sales roles signal GTM shifts, exec hires signal strategy changes\n   - **Blog \u002F content** — new positioning, case studies (reveal target customers), thought leadership pivots\n   - **Social media** — founder posts, company announcements, community reactions\n   - **Review sites** — new reviews on G2, Capterra, Trustpilot (sentiment shifts)\n   - **Funding \u002F press** — Crunchbase alerts, press releases, media coverage\n2. **Set up the monitoring stack** — recommend tools and manual checks:\n   - **Automated:** Google Alerts (brand mentions), Visualping or ChangeTower (page change detection), Crunchbase alerts (funding), LinkedIn job alerts\n   - **Manual weekly scan:** pricing pages, changelogs, recent blog posts, latest job postings\n   - **Quarterly deep dive:** full `competitive-analysis` refresh\n3. **Run the scan** — check all sources for the monitoring period and flag changes.\n4. **Analyze signals** — for each change detected:\n   - What changed (factual description)\n   - What it signals (interpretation — are they moving upmarket? entering your segment? struggling with churn?)\n   - Threat level (none \u002F watch \u002F respond \u002F urgent)\n   - Recommended action (if any)\n5. **Generate the report** — produce a concise weekly\u002Fbiweekly competitor intel brief.\n\n## Output Format\n\n```markdown\n## Competitor Intel Brief — Week of [Date]\n\n### Summary\n[1-2 sentence overview: \"Quiet week. Competitor A shipped a free tier. No pricing changes elsewhere.\"]\n\n### Changes Detected\n\n**[Competitor A]**\n- **What changed:** [factual description]\n- **Signal:** [what this likely means strategically]\n- **Threat level:** [None \u002F Watch \u002F Respond \u002F Urgent]\n- **Recommended action:** [what to do, if anything]\n\n**[Competitor B]**\n- No changes detected this period.\n\n### Job Posting Signals\n| Competitor | New Roles | Signal |\n|-----------|-----------|--------|\n| [A] | 3 enterprise AEs, VP Sales | Moving upmarket |\n| [B] | ML engineer, data scientist | Building AI features |\n\n### Emerging Patterns\n- [Pattern observed across multiple competitors or over time]\n\n### Action Items\n- [ ] [Specific action for the founder]\n```\n\n## Frameworks & Best Practices\n\n**Reading job postings as strategy signals:**\n| Role Type | What It Signals |\n|-----------|----------------|\n| Enterprise AEs \u002F Sales Engineers | Moving upmarket or launching enterprise tier |\n| DevRel \u002F Community Manager | Investing in developer ecosystem or community-led growth |\n| ML\u002FAI Engineers | Building AI features or data products |\n| International roles \u002F specific geo | Expanding to new markets |\n| Product Marketing Manager | Repositioning or launching new product lines |\n| Head of Partnerships | Platform\u002Fecosystem strategy |\n| Lots of support hires | Scaling fast or struggling with quality |\n\n**Threat level framework:**\n- **None:** Routine activity, no impact on you\n- **Watch:** Interesting move, could affect you in 3-6 months — add to next strategy discussion\n- **Respond:** Directly affects your positioning, pricing, or target market — needs a plan within 2 weeks\n- **Urgent:** Launches directly competing feature, undercuts your pricing, or targets your exact ICP — needs immediate response\n\n**Common mistakes:**\n- Monitoring too many competitors (pick 3-5, not 15)\n- Reacting to every move instead of identifying patterns\n- Confusing competitor activity with competitor success (they shipped a feature — doesn't mean it works)\n- Ignoring indirect competitors and new entrants\n- Not archiving snapshots (you'll want to see how their pricing page looked 6 months ago)\n\n## Related Skills\n- `competitive-analysis` — for the initial deep dive and periodic refresh\n- `daily-product-digest` — for broader market monitoring beyond specific competitors\n- `review-mining` — for tracking competitor sentiment on review platforms\n- `market-research` — for understanding market shifts driving competitor behavior\n\n## Examples\n\n**Prompt:** \"Set up competitor monitoring for our 4 main competitors in the email marketing space.\"\n\n**Good output includes:** Monitoring surface for each competitor (pricing pages, changelogs, job boards, blogs), recommended tool stack for automated alerts, and a template for the weekly intel brief.\n\n**Prompt:** \"What have our competitors been up to this week?\"\n\n**Good output includes:** Scan of changelogs, pricing pages, blog posts, job postings, and social accounts for each tracked competitor. Flagged changes with signal interpretation and threat levels. Actionable summary.\n","# Competitor Monitoring\n\n## When to Use\n- Founder wants to know when competitors change pricing, ship features, or raise funding\n- Founder wants a recurring \"what changed this week\" scan of competitor activity\n- Founder wants to detect strategic shifts from competitor job postings, blog posts, or product updates\n- Founder wants to stay informed without manually checking 10 websites daily\n\nThis is the **recurring sibling** of `competitive-analysis` (one-time deep dive). Use this skill for ongoing monitoring, not initial research.\n\n## Context Required\n- List of 3-7 competitors to track (names, websites, product URLs)\n- What the founder cares about most (pricing, features, positioning, hiring, funding, content)\n- Monitoring frequency (weekly recommended for early-stage, biweekly for established markets)\n- The founder's own positioning (to flag threats and opportunities)\n\n## Workflow\n\n1. **Define the monitoring surface** — for each competitor, identify what to watch:\n   - **Pricing page** — plan changes, new tiers, free plan adjustments\n   - **Changelog \u002F release notes** — new features, deprecations, platform shifts\n   - **Job postings** — engineering roles signal product direction, sales roles signal GTM shifts, exec hires signal strategy changes\n   - **Blog \u002F content** — new positioning, case studies (reveal target customers), thought leadership pivots\n   - **Social media** — founder posts, company announcements, community reactions\n   - **Review sites** — new reviews on G2, Capterra, Trustpilot (sentiment shifts)\n   - **Funding \u002F press** — Crunchbase alerts, press releases, media coverage\n2. **Set up the monitoring stack** — recommend tools and manual checks:\n   - **Automated:** Google Alerts (brand mentions), Visualping or ChangeTower (page change detection), Crunchbase alerts (funding), LinkedIn job alerts\n   - **Manual weekly scan:** pricing pages, changelogs, recent blog posts, latest job postings\n   - **Quarterly deep dive:** full `competitive-analysis` refresh\n3. **Run the scan** — check all sources for the monitoring period and flag changes.\n4. **Analyze signals** — for each change detected:\n   - What changed (factual description)\n   - What it signals (interpretation — are they moving upmarket? entering your segment? struggling with churn?)\n   - Threat level (none \u002F watch \u002F respond \u002F urgent)\n   - Recommended action (if any)\n5. **Generate the report** — produce a concise weekly\u002Fbiweekly competitor intel brief.\n\n## Output Format\n\n```markdown\n## Competitor Intel Brief — Week of [Date]\n\n### Summary\n[1-2 sentence overview: \"Quiet week. Competitor A shipped a free tier. No pricing changes elsewhere.\"]\n\n### Changes Detected\n\n**[Competitor A]**\n- **What changed:** [factual description]\n- **Signal:** [what this likely means strategically]\n- **Threat level:** [None \u002F Watch \u002F Respond \u002F Urgent]\n- **Recommended action:** [what to do, if anything]\n\n**[Competitor B]**\n- No changes detected this period.\n\n### Job Posting Signals\n| Competitor | New Roles | Signal |\n|-----------|-----------|--------|\n| [A] | 3 enterprise AEs, VP Sales | Moving upmarket |\n| [B] | ML engineer, data scientist | Building AI features |\n\n### Emerging Patterns\n- [Pattern observed across multiple competitors or over time]\n\n### Action Items\n- [ ] [Specific action for the founder]\n```\n\n## Frameworks & Best Practices\n\n**Reading job postings as strategy signals:**\n| Role Type | What It Signals |\n|-----------|----------------|\n| Enterprise AEs \u002F Sales Engineers | Moving upmarket or launching enterprise tier |\n| DevRel \u002F Community Manager | Investing in developer ecosystem or community-led growth |\n| ML\u002FAI Engineers | Building AI features or data products |\n| International roles \u002F specific geo | Expanding to new markets |\n| Product Marketing Manager | Repositioning or launching new product lines |\n| Head of Partnerships | Platform\u002Fecosystem strategy |\n| Lots of support hires | Scaling fast or struggling with quality |\n\n**Threat level framework:**\n- **None:** Routine activity, no impact on you\n- **Watch:** Interesting move, could affect you in 3-6 months — add to next strategy discussion\n- **Respond:** Directly affects your positioning, pricing, or target market — needs a plan within 2 weeks\n- **Urgent:** Launches directly competing feature, undercuts your pricing, or targets your exact ICP — needs immediate response\n\n**Common mistakes:**\n- Monitoring too many competitors (pick 3-5, not 15)\n- Reacting to every move instead of identifying patterns\n- Confusing competitor activity with competitor success (they shipped a feature — doesn't mean it works)\n- Ignoring indirect competitors and new entrants\n- Not archiving snapshots (you'll want to see how their pricing page looked 6 months ago)\n\n## Related Skills\n- `competitive-analysis` — for the initial deep dive and periodic refresh\n- `daily-product-digest` — for broader market monitoring beyond specific competitors\n- `review-mining` — for tracking competitor sentiment on review platforms\n- `market-research` — for understanding market shifts driving competitor behavior\n\n## Examples\n\n**Prompt:** \"Set up competitor monitoring for our 4 main competitors in the email marketing space.\"\n\n**Good output includes:** Monitoring surface for each competitor (pricing pages, changelogs, job boards, blogs), recommended tool stack for automated alerts, and a template for the weekly intel brief.\n\n**Prompt:** \"What have our competitors been up to this week?\"\n\n**Good output includes:** Scan of changelogs, pricing pages, blog posts, job postings, and social accounts for each tracked competitor. Flagged changes with signal interpretation and threat levels. Actionable summary.\n",{"name":5,"reads":24,"origin":26,"related":27,"description":7},[25],"startup-context","startup",[28,29,30,31],"competitive-analysis","daily-product-digest","review-mining","market-research","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fstartup--competitor-monitoring",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-12 23:12:27",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill competitor-monitoring",{"tool":48,"command":49},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill competitor-monitoring",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill competitor-monitoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fstartup--competitor-monitoring\u002FSKILL.md",true,[],[57,65,72,80,88,96],{"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":61,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"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},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\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":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\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":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"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":99,"categories":100,"keywords":101,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]