agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/daily-growth-operator/SKILL.md

daily-growth-operator

Skill4 starsChanged 6 months agoMITView on GitHub

Run the daily review workflow, keep a prioritized improvement queue, and monitor unresolved issues. Use when executing daily marketing operations and task management.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    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:

    Run the daily review workflow, keep a prioritized improvement queue, and monitor unresolved issues.

    line 9
  2. Distinctive:

    When conducting the daily review of active campaigns, ad sets, ads, landing pages, and funnel performance.

    line 12
  3. Distinctive:

    When identifying what changed, what improved, what worsened, and what needs attention.

    line 13
  4. Distinctive:

    When prioritizing tasks for the day (e.g., pausing losing ads, scaling winning ones, testing new creatives).

    line 14
  5. Distinctive:

    When monitoring unresolved issues (e.g., broken tracking, low conversion rates).

    line 15
  6. Distinctive:

    Prioritize Tasks: Create a prioritized list of actions for the day (e.g., pause losing ads, scale winning ones, test new creatives).

    line 28
  7. Distinctive:

    Update Queue: Add any new tasks or unresolved issues to the improvement queue.

    line 29
  8. Distinctive:

    Never ignore unresolved issues.

    line 43
  9. Distinctive:

    Use evidence from performance data to justify all actions.

    line 44
  10. Distinctive:

    If a critical issue arises (e.g., broken tracking, sudden drop in conversion rate), escalate immediately to the user.

    line 47
  11. Distinctive:

    If a task requires significant resources or time, request approval before proceeding.

    line 48

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

Daily Growth Operator

Purpose

Run the daily review workflow, keep a prioritized improvement queue, and monitor unresolved issues. Ensure all marketing operations are executed efficiently and effectively.

When to Use This Skill

  • When conducting the daily review of active campaigns, ad sets, ads, landing pages, and funnel performance.
  • When identifying what changed, what improved, what worsened, and what needs attention.
  • When prioritizing tasks for the day (e.g., pausing losing ads, scaling winning ones, testing new creatives).
  • When monitoring unresolved issues (e.g., broken tracking, low conversion rates).

Inputs Required

  • Daily performance data (spend, impressions, CPM, CTR, CPC, leads, CPL, etc.).
  • Downstream funnel data (landing page views, form completions, booked calls, qualified leads).
  • Current task list and improvement queue.
  • Any unresolved issues from previous days.

Step-by-Step Workflow

  1. Review Performance: Analyze daily data for all active campaigns, ad sets, and ads.
  2. Identify Changes: Note any significant shifts in performance (e.g., sudden drop in CTR, spike in CPL).
  3. Diagnose Issues: Determine the root cause of any problems (e.g., creative fatigue, audience overlap, broken tracking).
  4. Prioritize Tasks: Create a prioritized list of actions for the day (e.g., pause losing ads, scale winning ones, test new creatives).
  5. Update Queue: Add any new tasks or unresolved issues to the improvement queue.
  6. Execute Actions: Implement the prioritized tasks (e.g., pause ads, launch new tests).
  7. Monitor Progress: Track the impact of the actions taken and adjust as needed.

Output Format

Provide a structured daily review report containing:

  • Performance Summary: High-level overview of daily trends.
  • Issues Identified: Any problems or anomalies detected.
  • Prioritized Tasks: A list of actions to take today.
  • Improvement Queue: A list of tasks for future execution.
  • Unresolved Issues: Any ongoing problems that need attention.

Decision Rules

  • Always prioritize tasks by highest impact, lowest effort, fastest feedback loop, and strongest expected lift.
  • Never ignore unresolved issues; keep them visible until they are resolved.
  • Use evidence from performance data to justify all actions.

Escalation Rules

  • If a critical issue arises (e.g., broken tracking, sudden drop in conversion rate), escalate immediately to the user.
  • If a task requires significant resources or time, request approval before proceeding.

Templates & Resources

  • checklists/daily-review.md: Checklist for daily account monitoring.
  • automations/task-management.md: Guidelines for managing tasks and the improvement queue.

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.