CtrlK
BlogDocsLog inGet started
Tessl Logo

routines

Use for a recurring unattended task (cron; pull data, open a PR, post a digest), or to test/dry-run a routine first. Explains authoring and testing via the routine tool.

69

Quality

84%

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

85%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 well-structured, actionable instruction skill with an explicit test-then-create workflow, validation checkpoints, and a feedback loop. It is held back only by placeholder args in the tool examples and a few sentences that could be trimmed.

DimensionReasoningScore

Conciseness

The body is largely lean and every section earns its place; the isolation-model bullets are dense but convey tool-specific safety constraints rather than generic Claude knowledge. Not a 5 because a few sentences (e.g. the long headless-approvals bullet) could be tightened; not a 3 because there is no padding or explanation of concepts Claude already knows.

4 / 5

Actionability

Provides concrete, executable tool calls with real signatures — 'routine(action="create", name=..., schedule=..., task=..., secrets=[...])', 'routine(action="test", ...)' — plus a concrete cron example ('"0 8 * * *" = daily 08:00 UTC'). Not a 5 because the examples use placeholder args (name=...) rather than a fully fleshed end-to-end example covering a common case.

4 / 5

Workflow Clarity

Clear sequence — author, dry-run/test, read output, fix and re-test, then create, then await user confirmation — with explicit validation (the test's {success, status, output}) and a feedback loop ('fix task/secrets and test again'). Not a 4 because validation checkpoints and the error-recovery loop are explicit, not merely implied.

5 / 5

Progressive Disclosure

A self-contained single-file skill (~60 lines) with no bundle files and no need for external references, organized into well-signaled sections (isolation model, authoring, testing, scheduling). Structure is clear and navigable; no nested or buried references. Matches the simple-skill exception for well-organized single-file content.

5 / 5

Total

18

/

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 that clearly states both the trigger conditions and the skill's purpose, with concrete example actions and natural vocabulary. It is held back only by slightly illustrative rather than exhaustive action coverage and minor synonym gaps.

DimensionReasoningScore

Specificity

Names the domain ('recurring unattended task', 'cron') and lists several concrete actions — 'pull data, open a PR, post a digest' plus 'test/dry-run a routine' — but stops short of comprehensive coverage of all routine use cases. Not a 5 because coverage is illustrative rather than exhaustive; not a 3 because multiple specific actions are named rather than 1-2.

4 / 5

Completeness

Explicitly answers 'when' ('Use for a recurring unattended task (cron; pull data, open a PR, post a digest), or to test/dry-run a routine first') and 'what' ('Explains authoring and testing via the routine tool') with concrete trigger phrases. Both halves are present and explicit, matching the top anchor; not a 4 because 'when' is concrete, not merely implied.

5 / 5

Trigger Term Quality

Strong natural terms — 'recurring unattended task', 'cron', 'pull data', 'open a PR', 'post a digest', 'dry-run' — that users would plausibly say. Not a 5 because common synonyms like 'schedule', 'automate', or 'every morning' are absent, leaving a few natural phrasings uncovered.

4 / 5

Distinctiveness Conflict Risk

A clear niche — recurring unattended cron routines in an isolated sandbox — with distinct triggers and a named 'routine' tool. Not a 5 because it overlaps slightly with recurring/interval concepts that other scheduling skills (e.g. a generic loop or reminder skill) might also claim.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
google/adk-samples
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.