Scheduling operations
Skill lensetek/Digital-Marketing-Agent_Skills/capabilities/scheduling-operations
Digital-Marketing-Agent_SkillsFrom the repository description
npx -y skills add lensetek/Digital-Marketing-Agent_Skills --skill scheduling-operationsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, 180 tokens by cl100k_base, as published. Nobody here has run it
Scheduling Operations Capability
When to Use
Use this capability for campaign calendars, reminders, publishing schedules, meeting scheduling, follow-up cadences, and automation timing plans.
Preferred Implementation
- Use calendar connectors, scheduling APIs, or local schedule files when available.
- Draft schedules first; creating calendar events or live reminders is a gated action.
- Use Computer Use only when a scheduling UI must be operated manually.
Inputs
- Schedule objective.
- Timezone.
- Date range.
- Cadence.
- Participants or channels.
- Approval status.
Outputs
- Campaign Schedule.
- Content Calendar Timing.
- Reminder Plan.
- Calendar Event Drafts.
- Approval Gate Notes.
Security and Ethics
- Do not expose private calendar details, meeting links, attendee emails, or scheduling tokens.
- Confirm timezone and date assumptions.
- Do not create or send invites without approval.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 180 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- Use calendar connectors, scheduling APIs, or local schedule files
- Draft schedules before creating events or reminders
- Use Computer Use only when a scheduling UI must be operated manually
- Confirm timezone and date assumptions
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.