CtrlK
BlogDocsLog inGet started
Tessl Logo

self-awareness

Claude Science's own session database schema and SDK surface for introspection via host.query(). Load this when you need to query your own conversation history, token usage, cost accounting, execution log, or artifact metadata beyond what host.frames()/host.artifacts() provide — e.g. "how many tokens has this session used", "what was my last tool call", "list every file I've written", "where are messages stored", "what tables can I query", "inspect frames.context_data", or any time you're about to PRAGMA-probe the Claude Science metadata DB to discover its schema.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, high-density reference skill: executable SQL examples, exact dialect/limit constraints, denied-table guidance with SDK alternatives, and a clear tool-routing table. The main improvement opportunities are trimming verbose SDK-table rows and splitting the schema catalog into a one-level-deep reference file.

Suggestions

Trim the behavioral parentheticals in the host.delegate and host.submit_output rows of the SDK table (backgrounding, interrupt semantics, bounce handling) into a short separate note or the relevant skill, keeping the table rows scannable.

Move the per-table column listings (frames, artifact_versions, execution_log, etc.) into a references/schema.md and keep SKILL.md to one-line table summaries plus the worked examples, so the overview file stays lean.

Add a brief explicit error-recovery note for the two documented failure modes (truncation → narrow columns / aggregate server-side; timeout → simplify the query) as a short checklist, making the feedback loops as actionable as the query guidance.

DimensionReasoningScore

Conciseness

The body is dense reference material that assumes Claude's competence — no SQLite tutorials, no basic-concept padding — with high information per line ('json_extract(col, $.key)', epoch-ms examples). A few spots could be trimmed, e.g. the long behavioral parentheticals in the host.delegate and host.submit_output SDK rows and the repeated 'only available via the repl tool' note.

4 / 5

Actionability

Four complete, copy-paste-ready worked examples ('SELECT COUNT(*) … SUM(total_cost) FROM frames', execution_log with json_array_length(e.files_written), artifacts JOIN artifact_versions) plus concrete introspection commands ('PRAGMA table_info(frames)', sqlite_master query) and exact limits (limit=1000, 2000-char cell cap, 5s timeout).

5 / 5

Workflow Clarity

This is a reference skill whose single action is unambiguous: run read-only SQL via the repl tool, with a clear sequence (dialect/limits → schema introspection → per-table queries) and built-in error-avoidance feedback ('truncated=True … narrow your columns', 'Aggregate server-side so the row cap can't undercount', prefer host.frames() over raw _messages). It stops short of an explicit validate-and-retry loop, so it fits 'clear sequence with most checkpoints present' rather than the full-checklist anchor.

4 / 5

Progressive Disclosure

The single file is well-sectioned ('Dialect and limits', 'Queryable tables' with per-domain subsections, 'Denied tables', 'Worked examples', 'SDK surface') and its only external pointers are to other skills ('load the customize skill') at one level deep. However, the ~150-line table/column catalog is all inline in SKILL.md; a references/schema.md split for the per-table column listings would move it to the top anchor.

4 / 5

Total

17

/

20

Passed

Description

100%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.

An exemplary description: it states what the skill does, when to load it, and gives concrete natural-language trigger phrases plus technical triggers, all in a distinct niche. The only theoretical nit is density, but every clause carries triggering or capability information rather than padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'query your own conversation history, token usage, cost accounting, execution log, or artifact metadata' — plus the concrete mechanism ('introspection via host.query()'), giving comprehensive coverage of the skill's domain with no vague filler.

5 / 5

Completeness

Both 'what' ('Claude Science's own session database schema and SDK surface for introspection via host.query()') and 'when' ('Load this when you need to query… e.g. [concrete trigger phrases]') are explicitly and clearly answered with concrete trigger examples.

5 / 5

Trigger Term Quality

It includes a rich set of natural phrases a user would actually say ('how many tokens has this session used', 'what was my last tool call', 'list every file I've written', 'where are messages stored', 'what tables can I query') alongside technical triggers like 'PRAGMA-probe', covering synonyms across both casual and expert vocabularies.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — introspecting Claude Science's own metadata DB — a scope no generic SQL or database skill would claim, and the explicit contrasts ('beyond what host.frames()/host.artifacts() provide') sharpen the boundary further.

5 / 5

Total

20

/

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
UnicomAI/wanwu
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.