CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-workflow-miner

Analyze recent Codex session evidence for repeated manual workflows and route them to skills, subagents, validators, or no artifact when Jamie asks what he keeps doing manually.

Quality

77%

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/agent-ops/session-workflow-miner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, largely actionable instruction skill with a clear sequenced workflow, explicit validation gates, and real one-level references. Its weaknesses are redundancy across Constraints/Creation Rules/Execution Boundaries/Anti-Patterns and the absence of a concrete collector invocation command.

Suggestions

Merge Constraints, Creation Rules, and the overlapping redaction rules in Execution Boundaries into a single section, and fold Anti-Patterns that duplicate Gotchas into one list, to cut roughly 20-30 lines.

Add the exact collector invocation command (or a pointer to the collector entrypoint) to Workflow step 1 so "Run or refresh the session collector into /tmp" is executable.

Reference references/task-profile.json from the body (or drop it from the bundle) so every bundled file is discoverable.

DimensionReasoningScore

Conciseness

Guardrail content is spread across four overlapping sections with direct duplication: "Keep created artifacts single-purpose, compact, and executable" (Constraints) versus "Keep created skills single-purpose and executable" (Creation Rules), and redaction rules stated in both Execution Boundaries ("Redact secrets/sensitive data by default") and Constraints ("Redact secrets, tokens, API keys, credentials, PII..."). Anti-Patterns largely restates Gotchas. It is efficient in the sense of not explaining known concepts, but noticeably more than minor trimming is needed to consolidate, so it sits at the 3 anchor rather than 4.

3 / 5

Actionability

Mostly executable guidance: concrete paths (~/.agents/session-collector/, /tmp), named bundle files (aggregate.json, skillify-candidates.json, skill-refactor-handoffs.json), a named existing-owners table with specific skills (pr-green-sweep, autofox triage, technical-writer), a copy-ready YAML output template, and exact validation commands (./bin/ask skills audit ... --level strict --json --robot). It is not a 5 because step 1 ("Run or refresh the session collector into /tmp using a sandbox-safe cache path") never gives an actual command to invoke the collector.

4 / 5

Workflow Clarity

The 8-step Workflow is clearly sequenced with explicit checkpoints ("Validate the new artifact with the repo's narrowest available gate") and a dedicated Failure Mode section ("If validation fails, stop at the first failed gate, classify the failure"). It stops short of the 5 anchor because there is no fix-and-revalidate feedback loop, and the collector-run step is abstract rather than a concrete checkpoint.

4 / 5

Progressive Disclosure

The body is well sectioned with clearly signaled one-level references ("See references/contract.yaml for the compact contract and references/evals.yaml for smoke cases"), both of which exist in the bundle. It is not a 5 because the ~170-line body inlines material (Examples, Existing Owners table) that could be referenced out, and the bundled references/task-profile.json is never referenced from the body.

4 / 5

Total

15

/

20

Passed

Description

75%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 solid description: specific domain, concrete routing outcomes, an explicit trigger clause, and third-person voice. Its main limitation is single-phrasing trigger coverage and no mention of the inventory/reuse-first behavior that distinguishes it from skill-creation skills.

Suggestions

Add one or two more concrete trigger phrasings to the when clause, e.g. "or when deciding which repeated tasks should become skills, subagents, or validators".

Mention the reuse-first behavior ("route them to skills, subagents, validators, or no artifact when one already exists") to sharpen distinctiveness from generic skill-creation skills.

DimensionReasoningScore

Specificity

The description names its domain ("Analyze recent Codex session evidence for repeated manual workflows") and lists several concrete routing outcomes ("route them to skills, subagents, validators, or no artifact"). It falls short of the 5 anchor because it omits inventorying existing owners and recommending-only coverage that the body actually performs, and exceeds the 3 anchor's 1-2 action scope.

4 / 5

Completeness

Both what ("Analyze recent Codex session evidence ... and route them to skills, subagents, validators, or no artifact") and an explicit when clause ("when Jamie asks what he keeps doing manually") are present, matching the 4 anchor. It is not a 5 because the when covers only a single trigger phrasing rather than multiple concrete trigger phrases as in the 5 example.

4 / 5

Trigger Term Quality

It includes natural phrases a user would say, notably "repeated manual workflows", "skills", "subagents", and the direct trigger "when Jamie asks what he keeps doing manually". A few natural synonyms users might say (e.g. "repeated tasks", "automate", "session review") are missing, so it fits the good-but-not-comprehensive 4 anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

The Codex session-mining niche plus the distinctive trigger ("what he keeps doing manually") and the "no artifact when reuse is better" outcome give it a clear niche with only minor overlap risk against generic skill-creation skills, fitting the 4 anchor. It is written in third person, so no voice penalty applies.

4 / 5

Total

16

/

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

jscraik/Agent-Skills

Path

Skills/agent-ops/session-workflow-miner/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.