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 ./codex/plugins/agentlas-core-engine-meta-agent/runtime-support/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 body is a compact, well-structured set of instructions with a clear review-gated workflow and strong safety rules, and it avoids teaching known concepts. Its main weaknesses are unspecified execution machinery (scaffold, registration, verify gates) and canonical references that point to files not present in the skill bundle.

Suggestions

Specify what the "verify gates" and "local registration" concretely involve (commands or checks) so step 5 is executable rather than deferred.

Either bundle the canonical route details (e.g., under references/) or inline the essential parts of modes/session-agent-builder.md and agents/40-session-agent-builder/agent.md so the referenced paths resolve within the skill.

State the interactive-vs-terminal boundary once (in the intro) and drop the repeated restatement at the end of the Optional terminal route section.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and explains no background concepts, but the interactive-vs-terminal boundary is stated three times ("The important distinction is between an interactive host and the deterministic terminal utility", the intro bullets, and "This optional file route must never override the interactive current-session behavior"), which is minor repetition that could be trimmed. This fits the efficient-with-minor-trimmable-instances anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete details exist ("AGENTLAS_AGENT_HOME or ~/.agentlas/agents", the "IF / THEN / BECAUSE / AVOID / INSTEAD" rule syntax, and the "session preview|merge|ir|compile --input <session.jsonl>" command), but key execution steps are deferred to unspecified machinery: "route it through the existing package scaffold, complete, local registration, and verify gates" gives no commands or details, and the canonical files it cites are not part of the bundle. This matches the incomplete-guidance anchor rather than the mostly-executable one.

3 / 5

Workflow Clarity

The interactive route is a clear 5-step numbered sequence with an explicit owner-review feedback loop ("Support `Build Agent` and `Edit`; editing regenerates the report before any package write") and a no-overwrite guard ("never overwrite an existing child"). However, the "verify gates" in step 5 are named but never specified, leaving a minor validation gap characteristic of anchor 4 rather than the explicit-validation anchor 5.

4 / 5

Progressive Disclosure

Sections are well organized (Interactive route, Generalization and safety, Optional terminal route, Output), but the body's canonical references ("modes/session-agent-builder.md" and "agents/40-session-agent-builder/agent.md") point to files outside the skill bundle, and no references/ directory exists, so the deferred details are not actually carried by the skill. References are present but neither clearly signaled as bundle files nor verifiable, matching anchor 3.

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 behaviors, but it lacks any explicit when-to-use trigger guidance and misses natural trigger synonyms like "session" or "chat". It reads as a boundary statement between interactive and terminal routes rather than a discoverable trigger description.

Suggestions

Add an explicit trigger clause such as "Use when the owner asks to turn this session/conversation into a reusable agent" to lift completeness above the cap of 3.

Include natural synonyms users would say ("session", "chat", "build an agent from this conversation") alongside the existing terms to improve trigger term coverage.

Mention one or two more concrete actions (e.g., generating a generalized session report with redaction of private identifiers) to broaden the specificity of capabilities listed.

DimensionReasoningScore

Specificity

"Turn the current interactive conversation into an owner-reviewed reusable Agentlas agent" and "accept JSON or JSONL" name the domain and two concrete actions, but coverage is not comprehensive (report generation, generalization, and safety behaviors are absent from the description). It lists 1-2 concrete actions rather than the several specific actions of anchor 4.

3 / 5

Completeness

The "what" is clear (turn the current conversation into an owner-reviewed reusable agent; accept explicit JSON/JSONL exports for terminal runs), but there is no "Use when..." clause or equivalent explicit trigger guidance for the primary interactive route, capping completeness at 3 per the judging guidelines; "when" is only weakly implied.

3 / 5

Trigger Term Quality

Terms like "interactive conversation", "reusable agent", "JSON or JSONL", and "terminal" are relevant, but common natural variations users would say ("session", "chat", "build an agent from this session") are missing, matching the some-relevant-keywords anchor rather than the good-coverage one.

3 / 5

Distinctiveness Conflict Risk

The niche of converting the current live conversation into a reusable agent is distinct and unlikely to trigger for unrelated skills, but there are no explicit trigger phrases and there is minor overlap risk with generic agent-creation or skill-creation skills, fitting anchor 4 rather than the fully distinct anchor 5.

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

codex/plugins/agentlas-core-engine-meta-agent/runtime-support/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.