memory-ticketing

Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/memory-ticketing/SKILL.md

Quality

Content

78%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 tight, well-structured overview with an explicit flow and validation/gate steps, respecting token budget admirably. Its main gap is actionability: it tells Claude what files and roles exist but not what a Memory Event or Ticket actually looks like, so execution would require inference.

Suggestions

Add a minimal example of a Memory Event and the resulting Memory Ticket (JSONL line) so the emit->wrap step is copy-paste concrete.

Show the expected shape of memory-map.json and vault-references.json entries, or link to a reference file containing them.

Add an explicit error-recovery branch for step 3 (e.g., 'If validation fails, return the ticket to the emitting worker with redaction notes') to close the feedback loop and lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized (Required Files, Flow, Never Store) with no padding or explanation of concepts Claude already knows; every line earns its place, matching the 5-anchor.	5 / 5
Actionability	It names concrete file paths and a role-based pipeline (Workers, Runtime, Memory Curator, PM Soul, Policy Gate), but provides no ticket/event schema, example JSONL entries, or command-level detail, leaving key execution details missing.	3 / 5
Workflow Clarity	A clear 5-step numbered sequence is present with validation built into step 3 ('validates, redacts, deduplicates') and an approval gate in step 5, but there is no explicit validate->fix->retry feedback loop or error-recovery checklist, keeping it below 5.	4 / 5
Progressive Disclosure	This is a simple, under-50-line skill with no need for external references and clean section organization (Required Files / Flow / Never Store), which per the rubric's simple-skill note qualifies for 5.	5 / 5
	Total	17 / 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 is specific, trigger-rich, and tightly scoped to a distinct niche, with an explicit 'Use when' clause and concrete artifact/file names. Its main weakness is that the 'what' is implied through an enumerated object list under a single 'adding' verb rather than stated as explicit capabilities.

Suggestions

Lead with an explicit capability statement (e.g., 'Creates and routes Memory Tickets across an agent repo') before the 'Use when' clause so 'what' is as explicit as 'when'.

Vary the action verbs beyond 'adding' (e.g., emit, validate, route, promote) to surface multiple concrete actions and lift specificity toward 5.

Add a couple of natural-user synonyms or short phrasings (e.g., 'memory routing', 'team-memory promotion') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names concrete artifacts and actions ('adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo') but relies on a single verb ('adding') applied to many objects rather than multiple distinct actions, so it sits just below the comprehensive 5-anchor.	4 / 5
Completeness	Has an explicit 'Use when ... to an agent repo' trigger with concrete phrases and an implied 'what' (managing memory ticketing artifacts); the 'what' is shown via the enumerated objects rather than stated as a capability, so it does not fully reach the explicit what+when 5-anchor.	4 / 5
Trigger Term Quality	Includes natural domain terms users would say ('Memory Events', 'Memory Tickets', 'PM Soul memory ownership', 'Memory Curator routing') plus concrete file names, giving good coverage; a few common synonyms or phrasings are missing, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	Targets a highly specific internal niche (memory ticketing with PM Soul, Memory Curator, Policy Gate) with distinct trigger artifacts, making conflict with other skills minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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/memory-ticketing/SKILL.md
Commit: a7988bb

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.