agentleFS
Sign inStart free
pendo-iopendo-io/Product-Loop/daily-digest-conductor/SKILL.md

daily-digest-conductor

Skill0 starsChanged 14 days agoMITView on GitHub

Deprecated alias, kept for one release after this skill was renamed to daily-digest. It holds no run logic of its own. Load it only when an old scheduled task or a person names daily-digest-conductor explicitly; it then hands off to daily-digest, or stands down when the new daily task already exists so nobody gets two digests. Never choose it for a request that does not name it; use daily-digest.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Never edit config.json, the activity log, or a scheduled task.

    line 23
  2. Distinctive:

    Never post a digest of its own.

    line 24
  3. Distinctive:

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

    line 25

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

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

What to do when invoked

  1. Stand down if the new task exists. On a scheduled (unattended) run, check the scheduler's task list for daily-digest-daily, or read <workspace>/.daily-digest/config.json and check schedule.task_id. If either shows daily-digest-daily, exit without posting anything. The new task delivers today's digest; posting here would send a second one.
  2. Otherwise hand off. If daily-digest is installed, follow it exactly as if it had been invoked with the same request and the same config. On an attended run, say once, first: "daily-digest-conductor is now called daily-digest; running that." Its first run migrates the saved config (with a backup) and offers to move the scheduled task to the new name.
  3. If daily-digest isn't installed, run nothing. Attended: say the skill was renamed and offer to install daily-digest from https://github.com/pendo-io/Product-Loop. Unattended: post one line, "Your daily digest skill was renamed to daily-digest and the new version isn't installed yet; install it to get your digest back."

Boundaries

  • Never edit config.json, the activity log, or a scheduled task. daily-digest owns all three, including the rename migration.
  • Never post a digest of its own.
  • Remove this folder in the next release, once no saved config or task 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