agentleFS
anmoba99anmoba99/pipedrive-claude-skills/skills/pd-morning-brief/SKILL.md

pd-morning-brief

Skill0 starsChanged 32 days agoMITView on GitHub

Daily brief for a Pipedrive user: today's and overdue activities, idle deals, deals with no next step, and a ranked top 3 actions. Use when the user asks what to do today, for a brief, or for a daily plan.

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:

    Follow pd-core rules (load pd-core if not loaded).

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

pd-morning-brief

Follow pd-core rules (load pd-core if not loaded).

Requires: Pipedrive Optional: Google Calendar (merge today's meetings), Slack (DM the brief, if opted in) Fallback: chat

Steps

  1. Context: me.id and stage names from cache (or getAccountContext once).
  2. Activities: getActivities owner_id=<me> done=false sort_by=due_date sort_direction=asc limit=50. Split into overdue, today, next 2 days. Ignore later.
  3. Deals: getDeals owner_id=<me> status=open sort_by=update_time sort_direction=asc limit=200 include_fields=[next_activity_id,undone_activities_count].
    • Incremental: if .pipedrive/last_run.json has pd-morning-brief from today, reuse and fetch only updated_since=<last_run>.
  4. Flags: idle >= stale_days (config, default 14), no next activity, expected close date passed. Use pd-core/scripts/pd_digest.py when more than about 20 deals.
  5. Calendar (if live): today's meetings, matched to deals by attendee email or org name. No match is fine.
  6. Rank top 3 actions: overdue on high-value deals first, then close-date-passed, then no-next-step on biggest deals. Industry pack (if set) may add signals, for example trial end dates for saas.
  7. Save last_run.json timestamp (if filesystem). Output.

Output

<Weekday date>. <n> due today, <n> overdue, <n> deals need attention.
Top 3:
1. <action verb> <deal/person> (<why, short>)
2. ...
3. ...
Today:
- 10:00 call Ana Silva, deal 1042 Acme rollout
Overdue:
- <activity> | deal | days late
Attention:
- <id> | <deal> | <stage> | <value> | idle <n>d | <flag>

Max 10 lines per section. More: "and <n> more, ask for full list". Manager asking for the team: suggest pd-pipeline-review instead.

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.