.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions.
Install Competitor Monitoring
$ npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shawnpang/startup-founder-skills competitor-monitoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/competitor-monitoring .claude/skills/competitor-monitoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "competitor-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoring into .claude/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shawnpang/startup-founder-skills competitor-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/competitor-monitoring .agents/skills/competitor-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "competitor-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoring into .agents/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shawnpang/startup-founder-skills competitor-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/competitor-monitoring .cursor/skills/competitor-monitoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "competitor-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoring into .cursor/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shawnpang/startup-founder-skills.git --path skills/competitor-monitoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shawnpang/startup-founder-skills competitor-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/competitor-monitoring .gemini/skills/competitor-monitoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "competitor-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoring into .gemini/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shawnpang/startup-founder-skills competitor-monitoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/competitor-monitoring .github/skills/competitor-monitoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "competitor-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoring into .github/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shawnpang/startup-founder-skills competitor-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/competitor-monitoring .opencode/skills/competitor-monitoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "competitor-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/competitor-monitoring into .opencode/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
competitor-monitoring- GitHub stars
- 343
- Token cost
- ~1.5k tokens
- SKILL.md length
- 611 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions.
- Works in 5 steps: Define the monitoring surface — for each… → Set up the monitoring stack — recommend… → Run the scan — check all sources for the… → …
- Wants to set up ongoing tracking of competitor activity — pricing changes
- SKILL.md covers When to Use, Context Required, Workflow and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Competitor Monitoring is an agent skill from shawnpang/startup-founder-skills. 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".
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Feature launches and release readiness. The repository describes itself as: AI agent skills for tech startup founders — fundraising, sales, product, recruiting, engineering, legal, ops, and growth. Works with Claude Code, Cursor, Codex, and any Agent… The licence is MIT.
When your agent uses it
- Wants to set up ongoing tracking of competitor activity — pricing changes
- Feature launches
- Public mentions
- The user mentions track competitors
Example prompts
- “track competitors”
- “what are competitors doing”
- “competitor alerts”
- “/competitor-monitoring”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Define the monitoring surface — for each competitor, identify what to watch
- Set up the monitoring stack — recommend tools and manual checks
- Run the scan — check all sources for the monitoring period and flag changes.
- Analyze signals — for each change detected
- Generate the report — produce a concise weekly/biweekly competitor intel brief.
What it can do on your machine
Read from SKILL.md and the folder at commit 4ad31b4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Competitor Monitoring loads about 1.5k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 611 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from shawnpang/startup-founder-skills at commit 4ad31b4, republished under its MIT licence (© shawnpang). 611 words, ~1,525 tokens.
Download SKILL.mdSave it as
.claude/skills/competitor-monitoring/SKILL.md (or your agent's skills folder).- name
- competitor-monitoring
- description
- 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".
- related
- competitive-analysis, daily-product-digest, review-mining, market-research
- reads
- startup-context
Competitor Monitoring
When to Use
- Founder wants to know when competitors change pricing, ship features, or raise funding
- Founder wants a recurring "what changed this week" scan of competitor activity
- Founder wants to detect strategic shifts from competitor job postings, blog posts, or product updates
- Founder wants to stay informed without manually checking 10 websites daily
This is the recurring sibling of competitive-analysis (one-time deep dive). Use this skill for ongoing monitoring, not initial research.
Context Required
- List of 3-7 competitors to track (names, websites, product URLs)
- What the founder cares about most (pricing, features, positioning, hiring, funding, content)
- Monitoring frequency (weekly recommended for early-stage, biweekly for established markets)
- The founder's own positioning (to flag threats and opportunities)
Workflow
- Define the monitoring surface — for each competitor, identify what to watch:
- Pricing page — plan changes, new tiers, free plan adjustments
- Changelog / release notes — new features, deprecations, platform shifts
- Job postings — engineering roles signal product direction, sales roles signal GTM shifts, exec hires signal strategy changes
- Blog / content — new positioning, case studies (reveal target customers), thought leadership pivots
- Social media — founder posts, company announcements, community reactions
- Review sites — new reviews on G2, Capterra, Trustpilot (sentiment shifts)
- Funding / press — Crunchbase alerts, press releases, media coverage
- Set up the monitoring stack — recommend tools and manual checks:
- Automated: Google Alerts (brand mentions), Visualping or ChangeTower (page change detection), Crunchbase alerts (funding), LinkedIn job alerts
- Manual weekly scan: pricing pages, changelogs, recent blog posts, latest job postings
- Quarterly deep dive: full
competitive-analysisrefresh
- Run the scan — check all sources for the monitoring period and flag changes.
- Analyze signals — for each change detected:
- What changed (factual description)
- What it signals (interpretation — are they moving upmarket? entering your segment? struggling with churn?)
- Threat level (none / watch / respond / urgent)
- Recommended action (if any)
- Generate the report — produce a concise weekly/biweekly competitor intel brief.
Output Format
## Competitor Intel Brief — Week of [Date]
### Summary
[1-2 sentence overview: "Quiet week. Competitor A shipped a free tier. No pricing changes elsewhere."]
### Changes Detected
**[Competitor A]**
- **What changed:** [factual description]
- **Signal:** [what this likely means strategically]
- **Threat level:** [None / Watch / Respond / Urgent]
- **Recommended action:** [what to do, if anything]
**[Competitor B]**
- No changes detected this period.
### Job Posting Signals
| Competitor | New Roles | Signal |
|-----------|-----------|--------|
| [A] | 3 enterprise AEs, VP Sales | Moving upmarket |
| [B] | ML engineer, data scientist | Building AI features |
### Emerging Patterns
- [Pattern observed across multiple competitors or over time]
### Action Items
- [ ] [Specific action for the founder]Show full SKILL.md (300 more words)Show less
Frameworks & Best Practices
Reading job postings as strategy signals:
| Role Type | What It Signals |
|---|---|
| Enterprise AEs / Sales Engineers | Moving upmarket or launching enterprise tier |
| DevRel / Community Manager | Investing in developer ecosystem or community-led growth |
| ML/AI Engineers | Building AI features or data products |
| International roles / specific geo | Expanding to new markets |
| Product Marketing Manager | Repositioning or launching new product lines |
| Head of Partnerships | Platform/ecosystem strategy |
| Lots of support hires | Scaling fast or struggling with quality |
Threat level framework:
- None: Routine activity, no impact on you
- Watch: Interesting move, could affect you in 3-6 months — add to next strategy discussion
- Respond: Directly affects your positioning, pricing, or target market — needs a plan within 2 weeks
- Urgent: Launches directly competing feature, undercuts your pricing, or targets your exact ICP — needs immediate response
Common mistakes:
- Monitoring too many competitors (pick 3-5, not 15)
- Reacting to every move instead of identifying patterns
- Confusing competitor activity with competitor success (they shipped a feature — doesn't mean it works)
- Ignoring indirect competitors and new entrants
- Not archiving snapshots (you'll want to see how their pricing page looked 6 months ago)
Related Skills
competitive-analysis— for the initial deep dive and periodic refreshdaily-product-digest— for broader market monitoring beyond specific competitorsreview-mining— for tracking competitor sentiment on review platformsmarket-research— for understanding market shifts driving competitor behavior
Examples
Prompt: "Set up competitor monitoring for our 4 main competitors in the email marketing space."
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.
Prompt: "What have our competitors been up to this week?"
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.
© shawnpang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/competitor-monitoring of shawnpang/startup-founder-skills.
Open the folder on GitHubat commit 4ad31b4
Compare with similar skills
Competitor Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Competitor Monitoring this skillshawnpang/startup-founder-skills | 343 | — | ~1.5k | Automated safety check: Pass | MIT | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from shawnpang/startup-founder-skills
All 50 skills in this repoAccelerator Application
shawnpang/startup-founder-skills
When the user wants to apply to startup accelerators, incubators, or fellowship programs.
Architecture Design
shawnpang/startup-founder-skills
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis.
Board Update
shawnpang/startup-founder-skills
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
Churn Analysis
shawnpang/startup-founder-skills
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.
Cicd Setup
shawnpang/startup-founder-skills
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".
Code Review
shawnpang/startup-founder-skills
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".
Related
Categories
Questions about Competitor Monitoring
What does Competitor Monitoring do?
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Competitor Monitoring is an agent skill from shawnpang/startup-founder-skills. When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions.
When should I use Competitor Monitoring?
Competitor Monitoring fits situations like: wants to set up ongoing tracking of competitor activity — pricing changes; feature launches; public mentions; the user mentions track competitors.
How do I install Competitor Monitoring in Claude Code?
Run `npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a claude-code`. Or copy the skill folder (skills/competitor-monitoring in shawnpang/startup-founder-skills) into .claude/skills/competitor-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Competitor Monitoring in Codex?
Run `npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a codex`. Or copy the skill folder (skills/competitor-monitoring in shawnpang/startup-founder-skills) into .agents/skills/competitor-monitoring in your project. Codex loads it when a task matches its description.
Can I use Competitor Monitoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shawnpang/startup-founder-skills --skill competitor-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitor-monitoring, .gemini/skills/competitor-monitoring, .github/skills/competitor-monitoring and .opencode/skills/competitor-monitoring in your project.
What does Competitor Monitoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Competitor Monitoring is instructions for the agent only.
Does Competitor Monitoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Competitor Monitoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Competitor Monitoring use?
Competitor Monitoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Competitor Monitoring use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Competitor Monitoring?
Skills that share tags, products or a category with Competitor Monitoring: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitor Monitoring?
shawnpang (a GitHub user) maintains it in shawnpang/startup-founder-skills, which has 343 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on March 16, 2026.
Source: shawnpang/startup-founder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.