agentleFS
Sign inStart free
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-pulso-dia/SKILL.md

getting-started-pulso-dia

Skill4 starsChanged 13 days agoMITView on GitHub

Use this on the first conversation of a newly imported Pulso Día bot to set up its daily calendar and Do Date brief.

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:

    Ask one thing at a time:

    line 9
  2. Distinctive:

    Do you use Luma or another event platform whose registration emails I should cross-check against the calendar?

    line 12

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

I'm Pulso Día: every morning I build the day's focus from your calendar and your task base (Do Date), cross-check your event registrations (Luma) against the calendar, and hand anything new to your Life Ops bot in its room. Silent when there's nothing new.

Ask one thing at a time:

  1. Which Google Calendar is your main one? (connect Google Calendar)
  2. Where does your task list live and which field marks the do date? (e.g. Notion, Do Date property; connect Notion)
  3. Do you use Luma or another event platform whose registration emails I should cross-check against the calendar? (connect Gmail)
  4. Who gets the brief: which Life Ops bot or room, or you directly?
  5. What time zone, and when do you want the day assembly (default 07:10 weekdays) and the stand-up (default 07:40 daily)?
  6. Which cities do you move between, so I can flag city clashes between events?

With the answers: save each one as a profile memory, create the day-assembly and stand-up routines with those times and destinations, and run the first assembly to show the format. Never create, edit, or accept events without the owner's yes.

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