Competitor Feedback logo

Competitor Feedback

CommunityPopular
zhitongblog
competitor-feedback

Scan competing markdown editors' user feedback (GitHub issues/discussions/releases + closed-source forums) and synthesize themes cross-referenced against SoloMD's own gaps and roadmap. Surfaces unmet demand SoloMD could win on, and features competitors ship that SoloMD lacks. Supports a "subscribe" mode that reports only what's new since the last scan. Use when asked to "check competitor feedback", "what are users complaining about in Obsidian/Logseq/etc.", "competitor watch", or "subscribe to competitors' GitHub".

Overview

Publisherzhitongblog
Repositorysolomd
Skill namecompetitor-feedback
Stars
1.2K
Forks
80
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by zhitongblog on GitHub. Read the source before you install it.

Installation

Install the Competitor Feedback AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/zhitongblog/solomd/tree/main/.agents/skills/competitor-feedback
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zhitongblog/solomd.git /tmp/solomd
mkdir -p .claude/skills
cp -r /tmp/solomd/.agents/skills/competitor-feedback .claude/skills/competitor-feedback
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Competitor Feedback in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Competitor Feedback on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Competitor Feedback is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Competitor feedback watch

Pulls real user feedback from SoloMD's competitors and turns it into a product signal: what their users want that we could win on, and what they ship that we lack.

Channels (which tools actually work)

The global AGENTS.md mentions an unzoo browser. The mcp__unzoo__* MCP tools are not installed — but unzoo IS available as a local REST API at http://127.0.0.1:9399 (a real headless Chromium: JS rendering, anti-bot, cookies). Use it via the bundled unzoo.sh wrapper, not MCP calls.

  • GitHub (primary, structured): the gh CLI, driven by scan.sh — gives reaction-sorted issue lists (best unmet-demand signal). This is the main channel.
  • Closed-source competitors (Typora, Obsidian, Bear, iA Writer, Tolaria…): no public issue API → use unzoo.sh to read their forums/Reddit: unzoo.sh fetch-web <forum-url> and unzoo.sh search-web "<name> bug …". unzoo.sh discover-rss <site> can find a feed to poll. WebSearch/WebFetch are fine fallbacks.
  • GitHub fallback: if gh/the GitHub API is rate-limited or EOFs (CN network), unzoo.sh search-github "<query>" / unzoo.sh fetch-github <owner> <repo> reach GitHub through the browser backend and often succeed when gh doesn't.
  • Check it's up first: unzoo.sh health → {"status":"ok"}. Endpoints accept url / query / owner+repo; responses are {success, data} JSON.

Steps

  1. Pick mode.

    • Full scan (default): bash .Codex/skills/competitor-feedback/scan.sh
    • Subscribe / incremental (only issues opened since last run): bash .Codex/skills/competitor-feedback/scan.sh new
    • Restrict to some competitors: scan.sh full Logseq SiYuan
    • Tune volume with LIMIT=12 scan.sh.

    The competitor registry is competitors.json (edit to add/remove). GitHub-hosted ones are fetched directly; the script prints the GitHub digest and then lists the closed-source competitors for you to handle in step 2. It also writes .last-scan so the next new run is truly incremental — that's the "subscribe" behaviour.

  2. Web channel for closed-source competitors (via unzoo — the real browser). unzoo.sh health first. Then for each closed-source competitor scan.sh listed: unzoo.sh fetch-web <forum/reddit url from competitors.json> and unzoo.sh search-web "<name> bug OR missing feature OR complaint <year>". (WebSearch/WebFetch are fallbacks if unzoo is down.) Extract recurring themes — don't dump raw posts.

  3. Synthesize — this is the point, not the raw list. Group everything into recurring themes (e.g. "sync conflicts", "mobile parity", "large-vault perf", "plugin breakage"). For each theme note which competitors it hits and rough volume (top-voted issue = strong signal).

  4. Cross-reference against SoloMD. Read docs/roadmap.md and recent SoloMD issues (gh issue list --repo zhitongblog/solomd --state open). Then output two ranked lists:

    • Win-on: pains competitors' users repeatedly hit that SoloMD already does better or could cheaply own (these are positioning/marketing + wedge opportunities).
    • Gaps: things competitors ship that SoloMD lacks and users clearly value (candidate roadmap items). Be honest about effort.
    • Flag any theme that overlaps SoloMD's own recent complaints (shared weak spot).
  5. Write the report to docs/competitor-feedback/YYYY-MM-DD.md (create the dir). Structure: TL;DR (3-5 bullets) → themes table → Win-on → Gaps → raw per-competitor appendix (the scan.sh output + web findings, for traceability). Keep the synthesis tight and opinionated; the founder reads the TL;DR first.

Notes

  • CN network flakes on the GitHub API — scan.sh already retries; if a competitor shows "(fetch failed)", just re-run it for that one (scan.sh full <name>).
  • This is a read-only research skill. It never posts to competitors' trackers.
  • Cadence suggestion: run scan.sh new weekly; it stays incremental via .last-scan.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Competitor Feedback AI skill do?

Scan competing markdown editors' user feedback (GitHub issues/discussions/releases + closed-source forums) and synthesize themes cross-referenced against SoloMD's own gaps and roadmap. Surfaces unmet demand SoloMD could win on, and features competitors ship that SoloMD lacks. Supports a "subscribe" mode that reports only what's new since the last scan. Use when asked to "check competitor feedback", "what are users complaining about in Obsidian/Logseq/etc.", "competitor watch", or "subscribe to competitors' GitHub".

Why use Competitor Feedback on TypingMind?

Because you install it once and use it with any model. Competitor Feedback is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Competitor Feedback in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zhitongblog/solomd/tree/main/.agents/skills/competitor-feedback. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Competitor Feedback?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Competitor Feedback?

As many as you like. As long as a model supports skills, you can use Competitor Feedback with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Competitor Feedback AI skill free?

Yes. It is published on GitHub by zhitongblog under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇