CtrlK
BlogDocsLog inGet started
Tessl Logo

speaking

Speaking ops: invites, keynotes, panels, Gmail/calendar, conferences.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/speaking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The content is highly actionable and well-structured, with concrete commands, templates, and explicit verification steps for batch sheet operations; it is held just below top marks by implicit error-recovery loops and time-sensitive parameters embedded in commands.

DimensionReasoningScore

Conciseness

The body is dense and low-padding: bullet heuristics, exact gog commands, a file template, and sheet headers with no concept explanations Claude already knows; the only mild drag is time-sensitive date parameters (e.g. 'after:2026-01-01', the 2026 calendar range) embedded directly in commands rather than flagged, which keeps it just below a 5.

4 / 5

Actionability

Guidance is copy-paste ready across the common cases: concrete `gog` command snippets with exact syntax and sheet ranges, a per-opportunity markdown template, exact sheet headers, and a `NNN-slug.md` naming convention.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced ('When adding an opportunity' 1-5, 'Before changing status' 1-5) and batch sheet writes include a validation checkpoint ('After writing, re-read the range and verify row count'), but the error-recovery loop (what to do when verification fails) is implicit rather than an explicit fix-and-retry cycle.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file (Sources, Scope, Evaluation, Verification, Repo Notes, Sheet Sync) with no nested bundle references; the only referenced paths are external user-project data files rather than skill documentation, so structure is good but there is no actual one-level-deep reference split to push it to a 5.

4 / 5

Total

17

/

20

Passed

Description

61%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.

The description is compact and identifies a clear, distinct niche with natural trigger terms, but it lists objects rather than actions and entirely omits a 'when to use' trigger clause, which caps completeness.

Suggestions

Add an explicit 'when to use' clause, e.g. 'Use when triaging Peter's speaking invites, keynotes, panels, or conference opportunities.'

Reframe the list around actions rather than nouns, e.g. 'Tracks, evaluates, and responds to speaking invites, keynotes, panels, and conferences via Gmail and Calendar.'

Include common synonyms users might say ('talks', 'fireside', 'speaker invites') to round out trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Speaking ops') and several concrete items ('invites, keynotes, panels, Gmail/calendar, conferences'), but these are nouns/objects rather than concrete actions, so it lands at the anchor that names the domain with limited actions rather than the one that lists several specific actions.

3 / 5

Completeness

It conveys a clear-enough 'what' via the colon-list, but there is no 'Use when...' clause or equivalent trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ('invites, keynotes, panels, conferences'), giving good keyword coverage; a few natural synonyms are missing (e.g. 'talks', 'fireside', 'speaker'), which keeps it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Speaking ops' with keynote/panel/conference triggers is a distinct niche with low conflict risk; the generic 'Gmail/calendar' mention introduces minor overlap with email/calendar skills, keeping it just below a 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
steipete/agent-scripts
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.