agentleFS
Sign inStart free
HyaxiaHyaxia/blogwatcher/SKILL.md

blogwatcher-cli

Skill149 starsChanged 10 months agoMITView on GitHub

Use when managing or interacting with favorite blogs via the BlogWatcher CLI—adding/removing blogs, scanning for new posts, listing articles, marking read/unread, or modifying related CLI behavior, scanning, storage, and tests.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 3 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the Cobra entry point in cmd/blogwatcher/main.go and internal/cli/.

    line 9
  2. Very specific:

    Use scanning pipeline packages in internal/scanner, internal/rss, and internal/scraper.

    line 11
  3. Very specific:

    Run locally with go run ./cmd/blogwatcher ....

    line 15
  4. Very specific:

    Add or adjust CLI commands in internal/cli/commands.go (Cobra options, arguments, output formatting).

    line 19
  5. Very specific:

    Put non-trivial logic in internal/controller so the CLI stays thin and testable.

    line 20
  6. Very specific:

    Update storage or schema in internal/storage/database.go and adjust model conversion in internal/model if needed.

    line 21
  7. Very specific:

    Update or add tests under internal/ or cmd/ for every feature change or addition.

    line 23
  8. Very specific:

    Run tests with go test ./....

    line 26
  9. Distinctive:

    If you add a feature, add tests and any necessary dummy data.

    line 27
  10. Distinctive:

    Keep tests focused on CLI behavior, controller logic, and scraper/RSS parsing outcomes.

    line 28
  11. Distinctive:

    When listing posts available for reading, always include the link to each post in the output.

    line 32
  12. Very specific:

    Keep error handling consistent with existing exceptions (BlogNotFoundError, BlogAlreadyExistsError, ArticleNotFoundError).

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BlogWatcher CLI

Quick Orientation

  • Use the Cobra entry point in cmd/blogwatcher/main.go and internal/cli/.
  • Route business logic through internal/controller and persistence through internal/storage.
  • Use scanning pipeline packages in internal/scanner, internal/rss, and internal/scraper.
  • Remember the default SQLite path is ~/.blogwatcher/blogwatcher.db (override with BLOGWATCHER_DB) and is created on demand.

Run Commands

  • Run locally with go run ./cmd/blogwatcher ....
  • Build with go build ./cmd/blogwatcher.

Change Workflow

  1. Add or adjust CLI commands in internal/cli/commands.go (Cobra options, arguments, output formatting).
  2. Put non-trivial logic in internal/controller so the CLI stays thin and testable.
  3. Update storage or schema in internal/storage/database.go and adjust model conversion in internal/model if needed.
  4. Modify scanning behavior in internal/scanner and its helpers (internal/rss, internal/scraper).
  5. Update or add tests under internal/ or cmd/ for every feature change or addition.

Test Guidance

  • Run tests with go test ./....
  • If you add a feature, add tests and any necessary dummy data.
  • Keep tests focused on CLI behavior, controller logic, and scraper/RSS parsing outcomes.

Output Conventions

  • Preserve user-friendly CLI output with colors and clear errors.
  • When listing posts available for reading, always include the link to each post in the output.
  • Keep error handling consistent with existing exceptions (BlogNotFoundError, BlogAlreadyExistsError, ArticleNotFoundError).

Example (posts available for reading)

Unread articles (2):

  [12] [new] Understanding Click Contexts
       Blog: Real Python
       URL: https://realpython.com/click-context/
       Published: 2025-11-02

  [13] [new] Async IO in Practice
       Blog: Test & Code
       URL: https://testandcode.com/async-io-in-practice/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free