Qdrant Monitoring
github/awesome-copilot
Guides Qdrant monitoring and observability setup. An agent skill from github/awesome-copilot.
When the user wants to monitor reviews, mentions, and community sentiment about their own product.
MITAuto-check passed
Install Sentiment Monitoring
$ npx skills add shawnpang/startup-founder-skills --skill sentiment-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shawnpang/startup-founder-skills sentiment-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/sentiment-monitoring .claude/skills/sentiment-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 "sentiment-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sentiment-monitoring into .claude/skills/sentiment-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentiment-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/sentiment-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 sentiment-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shawnpang/startup-founder-skills sentiment-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/sentiment-monitoring .agents/skills/sentiment-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 "sentiment-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sentiment-monitoring into .agents/skills/sentiment-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentiment-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 sentiment-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shawnpang/startup-founder-skills sentiment-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/sentiment-monitoring .cursor/skills/sentiment-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 "sentiment-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sentiment-monitoring into .cursor/skills/sentiment-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentiment-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/sentiment-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 sentiment-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shawnpang/startup-founder-skills sentiment-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/sentiment-monitoring .gemini/skills/sentiment-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 "sentiment-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sentiment-monitoring into .gemini/skills/sentiment-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentiment-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 sentiment-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 sentiment-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/sentiment-monitoring .github/skills/sentiment-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 "sentiment-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sentiment-monitoring into .github/skills/sentiment-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentiment-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 sentiment-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 sentiment-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/sentiment-monitoring .opencode/skills/sentiment-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 "sentiment-monitoring" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sentiment-monitoring into .opencode/skills/sentiment-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentiment-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
sentiment-monitoring- GitHub stars
- 343
- Token cost
- ~2k tokens
- SKILL.md length
- 838 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to monitor reviews, mentions, and community sentiment about their own product.
- Works in 7 steps: Set up the monitoring list — the founder… → Define the severity scale — categorize… → Scan platforms — check each platform on… → …
- Wants to monitor reviews
- 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
Sentiment Monitoring is an agent skill from shawnpang/startup-founder-skills. When the user wants to monitor reviews, mentions, and community sentiment about their own product. Also use when the user mentions "track our reviews", "what are people saying about us", "brand monitoring", "reputation management", or "review alerts".
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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 monitor reviews
- Community sentiment about their own product
- The user mentions track our reviews
- What are people saying about us
Example prompts
- “track our reviews”
- “what are people saying about us”
- “brand monitoring”
- “/sentiment-monitoring”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Set up the monitoring list — the founder provides which platforms to watch. For each platform, note
- Define the severity scale — categorize incoming sentiment
- Scan platforms — check each platform on the founder's list for new reviews, mentions, or discussions since the last scan.
- Analyze each finding — for every new review or mention
- Draft responses — for negative and critical reviews, draft a response that
- Flag patterns — if 3+ reviews mention the same issue, escalate it as a product issue, not just a review problem.
- Generate the sentiment report — summary of findings with trends.
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
Sentiment Monitoring loads about 2k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 838 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). 838 words, ~1,973 tokens.
Download SKILL.mdSave it as
.claude/skills/sentiment-monitoring/SKILL.md (or your agent's skills folder).- name
- sentiment-monitoring
- description
- When the user wants to monitor reviews, mentions, and community sentiment about their own product. Also use when the user mentions "track our reviews", "what are people saying about us", "brand monitoring", "reputation management", or "review alerts".
- related
- review-mining, feedback-synthesis, churn-analysis, community-discovery
- reads
- startup-context
Sentiment Monitoring
When to Use
- Founder wants to track what customers and the public are saying about their product
- Founder wants to catch bad reviews early and respond before they spread
- Founder wants to understand community sentiment trends over time
- Founder wants to monitor specific review platforms for new reviews
This is different from review-mining (mining competitor reviews for pain points). This skill monitors your OWN product's reputation.
Context Required
- Product name and any common misspellings or abbreviations
- Platforms to monitor — the founder must provide the list of places to watch. Common options:
- Product Hunt (product page reviews and comments)
- Google Maps / Google Business reviews
- G2, Capterra, TrustRadius
- Trustpilot
- App Store / Play Store
- Reddit mentions
- Twitter/X mentions
- Hacker News mentions
- Industry-specific forums
- Monitoring frequency (daily for post-launch, weekly for steady state)
- Response policy — does the founder want draft responses for negative reviews?
- Escalation threshold — what severity warrants immediate attention?
Workflow
- Set up the monitoring list — the founder provides which platforms to watch. For each platform, note:
- Direct URL to the product's review/listing page
- Current rating and review count (baseline)
- How to check for new reviews (RSS, manual, API, or alert tool)
- Define the severity scale — categorize incoming sentiment:
- Critical (respond within 24h): public accusations of data loss, security issues, billing fraud, or legal threats. 1-star reviews with detailed complaints that could go viral.
- Negative (respond within 48h): legitimate complaints about bugs, missing features, poor support, or pricing frustration. 1-2 star reviews.
- Mixed (respond within 1 week): 3-star reviews with constructive feedback. "Good product but..."
- Positive (acknowledge): 4-5 star reviews. Thank the reviewer, ask for referrals.
- Scan platforms — check each platform on the founder's list for new reviews, mentions, or discussions since the last scan.
- Analyze each finding — for every new review or mention:
- Platform and date
- Sentiment: positive / mixed / negative / critical
- Core issue: what specifically is the person saying (quote verbatim)
- Validity: is this a legitimate product issue, user error, or bad-faith review?
- Impact: how visible is this? (high-traffic platform, many upvotes, or buried)
- Pattern: does this match other recent complaints? (signals a systemic issue)
- Draft responses — for negative and critical reviews, draft a response that:
- Acknowledges the issue without being defensive
- Shows the complaint was heard and understood
- Offers a specific next step (DM, email, fix timeline)
- Is written in the founder's voice, not corporate PR speak
- Flag patterns — if 3+ reviews mention the same issue, escalate it as a product issue, not just a review problem.
- Generate the sentiment report — summary of findings with trends.
Output Format
## Sentiment Report — [Date Range]
### Overview
- **Reviews scanned:** [count across all platforms]
- **New since last scan:** [count]
- **Sentiment breakdown:** [X positive, Y mixed, Z negative, W critical]
- **Average rating trend:** [up/down/stable vs. last period]
### Critical & Negative Items (action required)
**[Platform] — [Star Rating] — [Date]**
> "[Verbatim quote or summary]"
- **Core issue:** [what they're actually complaining about]
- **Validity:** [Legitimate / User error / Bad faith]
- **Pattern:** [First mention / Recurring — also seen on X, Y]
- **Suggested response:**
> [Draft response in founder's voice]
### Emerging Patterns
| Issue | Mentions This Period | Platforms | First Seen | Trend |
|-------|---------------------|-----------|------------|-------|
| [Issue] | [count] | [platforms] | [date] | [new / growing / stable] |
### Positive Highlights
- [Platform]: "[positive quote]" — consider using as testimonial
- [Platform]: "[positive quote]" — share on social
### Recommended Actions
- [ ] Respond to [N] critical/negative reviews (drafts above)
- [ ] Investigate [issue] — mentioned [N] times across [platforms]
- [ ] Request reviews from happy customers to offset [negative trend]Show full SKILL.md (412 more words)Show less
Frameworks & Best Practices
Response principles for negative reviews:
- Speed matters — respond within 24-48 hours. Unanswered negative reviews signal "they don't care."
- Acknowledge, don't argue — "I hear you" beats "Actually, you're wrong" every time
- Take it offline — "I'd love to look into this — can you email me at founder@company.com?" moves the conversation out of public view
- Be the founder — sign with your name and title. "— Alex, CEO" hits differently than a generic support reply
- Fix the issue, then update — come back to the review after fixing the problem: "We shipped a fix for this last week"
Platform-specific notes:
| Platform | Review visibility | Response capability | Notes |
|---|---|---|---|
| Product Hunt | High (launch day) | Comments only | Critical during and after launch. Engage in comments actively. |
| Google Maps | High (local SEO) | Owner response | Directly affects local search ranking. Respond to everything. |
| G2 | High (B2B buyers) | Vendor response | Enterprise buyers read these. Detailed responses matter. |
| Trustpilot | High (consumer) | Business response | Invite happy customers to balance. TrustScore affects visibility. |
| App Store | High (affects downloads) | Developer response | Apple limits response frequency. Be concise. |
| Variable | Comment as user | Don't astroturf. Be transparent about who you are. |
When negative reviews are actually gifts:
- Specific, actionable complaints point to real product gaps — treat them as free user research
- A pattern of "love the product but X is broken" means you have product-market fit with a fixable issue
- No negative reviews at all usually means no one is using the product
Common mistakes:
- Monitoring without responding (worse than not monitoring)
- Getting defensive or arguing publicly with reviewers
- Only monitoring one platform (customers complain wherever they are, not where you're watching)
- Treating all negative reviews equally (a billing fraud accusation ≠ a UI complaint)
- Not feeding review insights back into the product roadmap
Related Skills
review-mining— for mining COMPETITOR reviews (this skill monitors YOUR reviews)feedback-synthesis— for synthesizing feedback patterns into product decisionschurn-analysis— negative reviews often correlate with churn signalscommunity-discovery— to find communities where people discuss your product
Examples
Prompt: "Set up monitoring for our reviews. We're on Product Hunt, G2, Trustpilot, and the App Store."
Good output includes: Monitoring checklist for all 4 platforms with current baselines, severity scale customized to the product, and a template for the weekly sentiment report.
Prompt: "We got 3 bad reviews on G2 this week. Help me respond."
Good output includes: Analysis of each review (core issue, validity, pattern detection), draft responses in the founder's voice, and a flag if the issues point to a systemic product problem.
© 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/sentiment-monitoring of shawnpang/startup-founder-skills.
Open the folder on GitHubat commit 4ad31b4
Compare with similar skills
Sentiment 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 |
|---|---|---|---|---|---|---|
| Sentiment Monitoring this skillshawnpang/startup-founder-skills | 343 | — | ~2k | Automated safety check: Pass | MIT | |
| Qdrant Monitoringgithub/awesome-copilot | 40k | 1 repos | ~276 | Automated safety check: Pass | MIT | |
| Sentiment Monitoringvivy-yi/xiaohongshu-skills | 481 | — | ~5.7k | Automated safety check: Pass | None | |
| Monitoring Capture ServicePostHog/posthog | 40k | — | ~5k | Automated safety check: Pass | Custom licence | |
| Monitoring Ingestion PipelinePostHog/posthog | 40k | — | ~9.1k | Automated safety check: Pass | Custom licence | |
| Agent Performance Monitorruvnet/ruflo | 74k | 2 repos | ~4.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Sentiment Monitoring
vivy-yi/xiaohongshu-skills
A skill your agent uses when monitoring brand sentiment on Xiaohongshu, tracking public opinion, managing reputation, responding to negative feedback, analyzing brand perception trends, or handling…
- Official
Monitoring Capture Service
PostHog/posthog
Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production.
- Official
Monitoring Ingestion Pipeline
PostHog/posthog
Guide for using the Grafana MCP to monitor and diagnose the Node.js ingestion pipeline workers in production.
Agent Performance Monitor
ruvnet/ruflo
Agent skill for performance-monitor - invoke with $agent-performance-monitor
Monitor Stream
ruvnet/ruflo
Stream live swarm events using the Monitor tool for real-time observability
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".
Questions about Sentiment Monitoring
What does Sentiment Monitoring do?
When the user wants to monitor reviews, mentions, and community sentiment about their own product. Sentiment Monitoring is an agent skill from shawnpang/startup-founder-skills. When the user wants to monitor reviews, mentions, and community sentiment about their own product.
When should I use Sentiment Monitoring?
Sentiment Monitoring fits situations like: wants to monitor reviews; community sentiment about their own product; the user mentions track our reviews; what are people saying about us.
How do I install Sentiment Monitoring in Claude Code?
Run `npx skills add shawnpang/startup-founder-skills --skill sentiment-monitoring -a claude-code`. Or copy the skill folder (skills/sentiment-monitoring in shawnpang/startup-founder-skills) into .claude/skills/sentiment-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Sentiment Monitoring in Codex?
Run `npx skills add shawnpang/startup-founder-skills --skill sentiment-monitoring -a codex`. Or copy the skill folder (skills/sentiment-monitoring in shawnpang/startup-founder-skills) into .agents/skills/sentiment-monitoring in your project. Codex loads it when a task matches its description.
Can I use Sentiment 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 sentiment-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/sentiment-monitoring, .gemini/skills/sentiment-monitoring, .github/skills/sentiment-monitoring and .opencode/skills/sentiment-monitoring in your project.
What does Sentiment Monitoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Sentiment Monitoring is instructions for the agent only.
Does Sentiment 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 Sentiment 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 Sentiment Monitoring use?
Sentiment 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 Sentiment Monitoring use?
About 2k tokens (SKILL.md is roughly 7.9k 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 Sentiment Monitoring?
Skills that share tags, products or a category with Sentiment Monitoring: Qdrant Monitoring (github/awesome-copilot, 40k stars), Sentiment Monitoring (vivy-yi/xiaohongshu-skills, 481 stars), Monitoring Capture Service (PostHog/posthog, 40k stars) and Monitoring Ingestion Pipeline (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sentiment 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.