CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

office-hours

Set up and run Claude Code office hours, including the calendar event when the champion's own calendar connector allows it. Use when a champion wants a regular time for teammates to bring problems.

Quality

85%

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

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

This is a tightly written instruction skill: concrete options and defaults, explicit consent gates for the one risky action (calendar event creation), and clean section structure with no padding. The only real gaps are slight redundancy in consent rules and thinner guidance for the agenda and write-up paths compared to setup.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no concept explanation ('Ask people to bring a task, not a topic'), but consent-handling rules appear in both the asking-protocol paragraph and the closing safety paragraph, so a little trimming is possible.

4 / 5

Actionability

Gives exact AskUserQuestion options with recommended-first ordering, concrete defaults (Thursday at 2pm, champion's timezone), an exact event field spec, and explicit fallbacks (numbered list without the tool; paste-ready details without a calendar connector) — fully executable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

The setup branch is clearly sequenced with an explicit consent checkpoint ('show the exact event... Create it only after "Create it"'), but the agenda and write-up branches are thin and there is no error-recovery feedback loop, so it falls just short of anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (Start here, Then, background), which merits a 5 under the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

78%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 clearly and explicitly states both capability and trigger condition in third person with no fluff. Its main weakness is incomplete capability coverage: the agenda, write-up, and FAQ reuse flows in the body are absent, and a few natural trigger synonyms are missing.

Suggestions

Add the remaining capabilities to the description, e.g. 'Set up and run Claude Code office hours — invite, question template, agendas, and session write-ups — including the calendar event when the champion's own calendar connector allows it.'

Add one or two natural trigger variations such as 'drop-in hours' or 'open help session' so the Use-when clause catches more phrasings a champion would actually say.

Tie the calendar mention more tightly to the office-hours context (e.g. 'the office-hours calendar event') to reduce overlap with generic calendar or scheduling skills.

DimensionReasoningScore

Specificity

Names the domain ('Set up and run Claude Code office hours') and a concrete action ('including the calendar event'), but omits the agenda, write-up, and FAQ capabilities the skill covers, so coverage gaps are more than minor.

3 / 5

Completeness

Explicitly answers both what ('Set up and run Claude Code office hours, including the calendar event') and when ('Use when a champion wants a regular time for teammates to bring problems') with a concrete trigger scenario.

5 / 5

Trigger Term Quality

Includes natural phrases a champion would say ('office hours', 'regular time', 'teammates to bring problems'), but misses common variations such as 'drop-in hours' or 'open help session'.

4 / 5

Distinctiveness Conflict Risk

'Claude Code office hours' with the champion context is a clear niche, but 'including the calendar event' creates minor overlap risk with generic calendar or scheduling skills.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

anthropics/claude-plugins-official

Path

plugins/champion-kit/skills/office-hours/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.