session-logs

Search and analyze your own session logs (older/parent conversations) using jq.

1.91x

Quality

—

Does it follow best practices?

Impact

94%

1.91x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, highly actionable, and well-organized for a single-purpose skill: it gives real executable queries against the documented schema with no fluff and no broken references. It earns top marks across all content dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean: it skips explaining what JSONL/jq/rg are and goes straight to the data structure and copy-paste queries, with every section (Trigger, Location, Structure, Common Queries, Tips) earning its tokens.	3 / 3
Actionability	Provides nine complete, executable bash/jq/rg code blocks targeting the real session path, each copy-paste ready rather than pseudocode, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A single-purpose read-only query skill with queries clearly organized and labeled by task and a logical find-then-inspect-then-extract progression; no destructive/batch operations so no validation loop is required per the simple-skills note.	3 / 3
Progressive Disclosure	Self-contained with well-organized sections and no external bundle files or nested references; the only references are to real on-disk artifacts (sessions.json, <session-id>.jsonl), so there is no monolithic or deeply-nested reference problem.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 and distinct, naming concrete actions and tooling for a well-scoped niche. Its main weakness is the absence of an explicit "Use when..." trigger clause and limited trigger-term variation, which cap completeness and trigger quality at 2.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks what was said in prior/parent chats, references older conversations, or wants to search session/chat history."

Broaden trigger terms to include natural variations like "chat history", "prior chats", or "what was said before" to improve coverage.

Keep the third-person voice and conciseness while expanding triggers, avoiding any first/second-person phrasing.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ("Search and analyze") plus the mechanism ("using jq") and the domain ("session logs", "older/parent conversations"), matching the multi-action anchor rather than the partial score-2 anchor.	3 / 3
Completeness	Clearly answers "what" but lacks an explicit "Use when..." trigger clause; the parenthetical only implies "when", so per the rubric rule a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Has natural phrasings ("session logs", "older/parent conversations") but offers only two variants and misses common variations like "chat history" or "prior chats", fitting the missing-common-variations anchor at score 2.	2 / 3
Distinctiveness Conflict Risk	"Your own session logs / older/parent conversations using jq" is a distinct niche with unlikely overlap, matching the clear-niche anchor at score 3.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: trpc-group/trpc-agent-go
Commit: 737835b

Reviewed: 3 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.