agentleFS
XakkiXakki/ai-agents-skills/skills/research-source-audit/SKILL.md

research-source-audit

Skill6 starsChanged 3 months agoMITView on GitHub

Monitor requested sources or subjects for material changes using supported interfaces. Use for recurring checks of pages, feeds or releases. RU: мониторинг источников.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create or change a schedule, store personal monitoring state or send notifications only when the user authorizes those effects through the …

    line 13

≈ “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

Research monitoring

Define the actual watchlist, sources, scope, review cadence, materiality criteria, baseline, destination and authorized actions. Distinguish a one-time research request from an explicit request to schedule recurring work. Check whether the runtime actually provides a suitable scheduling and persistence interface; do not assume one exists.

For each observation, retrieve permitted sources, record the time and provenance, normalize and deduplicate the underlying event, and distinguish material change from repeated coverage or stale content. Compare against the durable prior state only when that state is available and within scope. Report unknowns and partial coverage.

Create or change a schedule, store personal monitoring state or send notifications only when the user authorizes those effects through the available interface. A monitoring setup or a useful draft does not imply permission to contact others.

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.