agentleFS
Sign inStart free
pendo-iopendo-io/Product-Loop/attention-radar/SKILL.md

attention-radar

Skill0 starsChanged 14 days agoMITView on GitHub

Deprecated alias, kept for one release after this skill was renamed to digest-composer. It holds no composing logic of its own. Load it only when a person or a saved config names attention-radar explicitly; it then hands off to digest-composer. Never choose it for a request that does not name it, and never treat it as a digest composer when matching skills by role; use digest-composer.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Never compose a digest itself and never write anything.

    line 22
  2. Distinctive:

    Remove this folder in the next release, once no saved config uses the old name.

    line 24

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

Deprecated: renamed to digest-composer

This skill was renamed to digest-composer in version 1.1.0. This copy exists only so a habit or saved config that uses the old name keeps working for one release. It does no work of its own.

What to do when invoked

  1. If digest-composer is installed, follow it exactly as if it had been invoked with the same request and the same inputs. When a person invoked it, say once, first: "attention-radar is now called digest-composer; using that."
  2. If it isn't installed, compose nothing. Say the skill was renamed and offer to install digest-composer from https://github.com/pendo-io/Product-Loop.

Boundaries

  • Never compose a digest itself and never write anything.
  • The daily-digest conductor never runs this stub as its composer; it resolves digest-composer instead (its references/daily-run.md 3c).
  • Remove this folder in the next release, once no saved config uses the old name.

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