CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dayparting

Analyze hour-of-day and day-of-week performance and set ad schedules and bid modifiers to spend when conversions happen. Use when a user wants to optimize ad scheduling, set dayparting, find the best times to run ads, or cut spend during dead hours.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-sequenced instruction skill: numbered workflow, approval gates, post-apply confirmation, and a scheduled re-check, with concrete decision rules for each time slot. The only weakness is minor genericness around which platform tool to read from and how to check the plan schema.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — no explanation of what dayparting is, no padding, and every rule earns its place ("Watch for thin cells; a single quiet hour is not a trend"); there is nothing to trim, so it matches the 5 anchor rather than 4.

5 / 5

Actionability

Concrete tool call ("Confirm the account: `list_connected_accounts`") and precise decision rules ("CPA at or below target want to keep or gain bid"; "spend and clicks but no conversions are candidates to reduce or exclude"), but "the platform performance tool" and "unless the live plan schema supports them" stay generic, leaving minor execution gaps per the 4 anchor.

4 / 5

Workflow Clarity

Four clearly numbered steps with explicit validation checkpoints at every risky point — "confirm before shipping", "Apply on approval", "confirm after it is applied", and a re-check loop "Re-pull after a couple of weeks to check the pattern held" — so the batch-change validation cap does not bind and it matches the 5 anchor's feedback loop.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized numbered sections plus a Rules section and no need for external references; the single cross-reference ("see **kill-scale-rules**") is clearly signaled, so per the simple-skill exception this earns a 5.

5 / 5

Total

19

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, third-person voice, and an explicit 'Use when' clause with several natural trigger phrases. The only weaknesses are minor — a few missing trigger synonyms and slight overlap risk with general bid/budget optimization skills.

Suggestions

Add one or two more natural trigger synonyms users would say, e.g. "time targeting" or "ads convert better at certain hours", to lift trigger term coverage.

State the deliverable of the analysis (e.g. a per-slot schedule with bid modifiers and expected CPA shift) to close the small coverage gap in specificity.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Analyze hour-of-day and day-of-week performance", "set ad schedules", "set bid modifiers" — but coverage stops at analyze-and-set, with no mention of the output or verification side, matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage at 5.

4 / 5

Completeness

Explicitly answers both: what ("Analyze hour-of-day and day-of-week performance and set ad schedules and bid modifiers") and when ("Use when a user wants to optimize ad scheduling, set dayparting, find the best times to run ads, or cut spend during dead hours") with multiple concrete trigger phrases, matching the 5 anchor; not 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Good natural trigger phrases — "optimize ad scheduling", "set dayparting", "find the best times to run ads", "cut spend during dead hours" — a user would plausibly say these; not 5 because common variations like "time targeting", "hour-of-day performance", or "pause ads at night" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear dayparting niche with distinct triggers ("dayparting", "best times to run ads") but "optimize ad scheduling" and bid-modifier language overlaps with broader bid/budget optimization skills, fitting 'mostly distinct; minor overlap risk' rather than minimal conflict at 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Synter-Media-AI/plugin

Path

skills/dayparting/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.