CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

insight-report

Generate local Codex usage reports. Use when users ask for usage analytics, weekly insights, session summaries, telemetry patterns, or prompting help.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/insight-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is a lean, well-sectioned overview with an executable runner command, explicit fail-fast validation gates, and concrete deliverable/artifact specifications. The main gaps are duplicated fail-fast text across two sections, an unpersuasive generic reference to references/, and out-of-bundle deferred references that add navigation hops.

Suggestions

Merge the near-duplicate 'Failure mode' and 'Validation' sections into a single validation section (one statement of the gate sequence and blocker reporting), or drop the Philosophy section, to tighten conciseness.

Replace the generic 'Local contract, evals, and task profile: references/' pointer with per-file links (e.g., references/contract.yaml, references/evals.yaml, references/task-profile.json) so navigation is one clear hop.

Collapse the two external Infrastructure/references/deferred-skill-context/ pointers into a single clearly-labeled 'Archived full workflow' entry, or copy the needed details into the bundle so reference chains stay one level deep.

DimensionReasoningScore

Conciseness

The body is mostly tight and sectioned, but "Failure mode" ("Stop at the first failed evidence, prompt, JSON, HTML, or browser-navigation gate") and "Validation" ("Stop at the first failed evidence, prompt, JSON, or HTML gate") repeat the same sentence nearly verbatim, and "Philosophy" adds little. This matches 'mostly efficient but could be tightened' rather than the level-4 anchor with only minor trims.

3 / 5

Actionability

Concrete, copy-paste-ready command ("python3 Skills/agent-ops/insight-report/scripts/run_insight_report.py --days 7") with documented flag combinations (--prepare-only --no-open, --render-only --no-open), concrete artifact paths, and an enumerated list of required JSON keys. Falls short of 5 because the path assumes a specific repo layout and the Codex-authored JSON writing step is described only at a high level.

4 / 5

Workflow Clarity

The prepare → write → render → open sequence is present with explicit fail-fast validation gates ("Stop at the first failed evidence, prompt, JSON, HTML, or browser-navigation gate. Report the exact blocker and artifact path") and edge-case handling in Gotchas. Not a 5 because the sequence is spread across sections rather than presented as an ordered workflow with explicit feedback loops for fixing a failed gate and re-running.

4 / 5

Progressive Disclosure

The body stays overview-sized and links real bundle files (scripts/run_insight_report.py exists; references/ holds contract.yaml, evals.yaml, task-profile.json), but the references/ pointer is a generic directory mention rather than per-file links, and two of the four pointers ("Infrastructure/references/deferred-skill-context/agent-ops-insight-report/..." including a full original-SKILL.md) resolve outside the skill bundle, adding a second hop of reference chaining. This matches 'some structure, references present but not clearly signaled' better than the level-4 anchor.

3 / 5

Total

14

/

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.

A well-formed description that clearly states what the skill does and when to use it, with strong natural trigger terms. Its main weakness is thin action specificity (one verb) and a slightly over-broad 'prompting help' trigger.

DimensionReasoningScore

Specificity

"Generate local Codex usage reports" names the domain plus a single concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage. A score of 4 would require several specific actions listed (e.g., collecting evidence, validating JSON, rendering HTML), which the description does not enumerate.

3 / 5

Completeness

The description explicitly answers both: "Generate local Codex usage reports" (what) and "Use when users ask for usage analytics, weekly insights, session summaries, telemetry patterns, or prompting help" (when, with concrete trigger phrases). This is a direct match for the top anchor, clearly above the level-4 anchor where 'when' is less explicit.

5 / 5

Trigger Term Quality

"usage analytics, weekly insights, session summaries, telemetry patterns, or prompting help" gives good natural keyword coverage a user would actually say. Missing common synonyms and variations (e.g., "usage statistics", "my activity", "how am I using Codex"), so it falls short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

"local Codex usage reports" carves a clear niche with distinct analytics triggers, but the trailing "or prompting help" is generic and could overlap with general prompt-assistance skills, which is minor overlap risk. Not entirely minimal-conflict like the anchor-5 example whose triggers are all domain-anchored.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/insight-report/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.