CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-agent-builder

Turn the current interactive conversation into an owner-reviewed reusable Agentlas agent; accept JSON or JSONL only for explicit terminal and automation runs.

Quality

67%

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 ./.agents/skills/session-agent-builder/SKILL.md

The canonical home for this skill is session-agent-builder in agentlas-ai/Agentlas-OS

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 content is a lean, well-sequenced instruction-only skill with a genuine owner-review feedback loop, and its safety section is appropriately terse. Its main weaknesses are actionability gaps (unspecified 'verify gates', no report/prompt example) and a broken progressive-disclosure chain that defers to canonical files absent from the bundle.

Suggestions

Bundle (or inline) the content of `modes/session-agent-builder.md` and `agents/40-session-agent-builder/agent.md` under references/, or replace the dangling 'canonical route' pointers with the actual instructions.

Make the 'verify gates' concrete: list the exact commands or pass/fair checks to run after writing a package, mirroring the feedback-loop pattern already used for report review.

Add a short example of a generalized session report (one IF/THEN/BECAUSE/AVOID/INSTead rule and one redaction before/after) so the required output format is unambiguous.

DimensionReasoningScore

Conciseness

The body is dense with task-specific policy (five numbered interactive steps, a compact safety list, a one-line CLI synopsis) and avoids explaining concepts Claude already knows, matching 'efficient; minor instances of over-explanation'. It is not a 5 because of slight padding such as restating the interactive/terminal distinction twice ('The important distinction is...' then again in 'This optional file route must never override...').

4 / 5

Actionability

Guidance includes a concrete CLI invocation ('session preview|merge|ir|compile --input <session.jsonl>') and specific report requirements ('IF / THEN / BECAUSE / AVOID / INSTEAD rules'), but key directives defer to unspecified machinery — 'route it through the existing package scaffold, complete, local registration, and verify gates' names no concrete gate or command. No example report or generated-prompt template is given, and the two 'canonical route' files are not in the skill bundle, so the referenced detail cannot actually be consulted. This fits 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The interactive route is a clearly sequenced 5-step process with an explicit owner-review checkpoint and feedback loop ('Show the report for owner review... editing regenerates the report before any package write') plus a verify gate before completion, matching 'clear sequence with most checkpoints present'. It falls short of level 5 because the verification gates themselves are never specified (no command or pass/fail criterion), so error recovery inside step 5 is implicit.

4 / 5

Progressive Disclosure

Sections are well organized (Interactive route, Generalization and safety, Optional terminal route, Output), but the body's opening pointers — 'Use `modes/session-agent-builder.md` and `agents/40-session-agent-builder/agent.md` as the canonical route' — reference files that do not exist in the skill bundle (references/, scripts/, assets/ are all absent), so the primary navigation path is dangling. That fits 'references present but not clearly signaled' in effect: the structure is good, but the disclosure chain breaks at the first hop.

3 / 5

Total

14

/

20

Passed

Description

53%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 communicates a clear, distinctive capability with two concrete actions, but it lacks an explicit 'Use when...' trigger clause and natural trigger terms like 'session', which caps completeness and trigger-term quality at the midpoint. Adding explicit trigger guidance with user-natural phrasing would lift it to the strong tier.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the owner asks to turn this conversation/session into a reusable agent, or when a terminal run supplies a session export.'

Include natural synonyms users would actually say — 'session', 'chat', 'build an agent from this conversation' — and drop or contextualize the jargon term 'Agentlas'.

Mention one or two more concrete capabilities (e.g., generating a generalized, redacted session report for owner review) to round out coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Turn the current interactive conversation into an owner-reviewed reusable Agentlas agent") plus one supporting action ("accept JSON or JSONL only for explicit terminal and automation runs"), which matches the '1-2 concrete actions, but not comprehensive' anchor. It omits core capabilities like report generation, generalization/redaction, and validation gates, so it is not the 'several specific actions' of level 4.

3 / 5

Completeness

The 'what' is clear (turn the current conversation into an owner-reviewed reusable agent), but there is no 'Use when...' clause or equivalent explicit trigger guidance for the primary interactive route; "for explicit terminal and automation runs" only conditions the secondary file-input route. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ("conversation", "agent", "reusable", "terminal", "automation", "JSON or JSONL") but common variations are missing — notably "session" (the skill's own core concept), "chat", and phrases like "build an agent from this". "Agentlas" is product jargon rather than a term a user would naturally say, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche is clear and narrow — converting the current live conversation into a reusable agent, with an explicit terminal/automation distinction — so overlap risk with other skills is minor. It stops short of the level-5 anchor because it lacks the explicit distinct trigger phrases ('Use when...') that the level-5 example carries.

4 / 5

Total

13

/

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

agentlas-ai/Agentlas-OS

Path

.agents/skills/session-agent-builder/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.