slackdump-sqlite3

Guidance for querying a Slackdump SQLite3 database directly via the sqlite3 CLI.

Quality

65%

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 ./cmd/slackdump/internal/mcp/assets/skills/slackdump-sqlite3/SKILL.md

Quality

Content

68%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 lean, actionable, and well-structured, with concrete SQL covering the difficult latest-version retrieval cases. Its main gap is the absence of explicit validation/verification checkpoints for a database skill, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints, e.g. verify the slackdump.sqlite path exists and confirm the intended CHUNK.TYPE_ID before running retrieval queries.

Tighten the SQL blocks by removing the 'WHERE 1=1' / 'JOIN ... ON 1=1' padding and clearly documenting the [PLACEHOLDER] substitution convention.

Consider moving the two large latest-version SQL queries into a referenced file (e.g. references/queries.sql) to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean with targeted tables, notes, and ready-to-use SQL and little padding, but the generated-style 'WHERE 1=1'/'JOIN ON 1=1' padding and [PLACEHOLDER] tokens add minor noise, fitting 'efficient; minor instances that could be trimmed'.	4 / 5
Actionability	Provides executable SQL for the two hardest queries plus pragmas and a JSON_EXTRACT example, with clearly marked [CHANNEL_ID]/[PARENT_MESSAGE_ID] parameters, but placeholders require substitution and no validation example is given, matching 'mostly executable guidance; minor gaps'.	4 / 5
Workflow Clarity	Steps are sequenced (locate DB, read-only constraint, pragmas, tables, chunk types, latest-version retrieval), but this database-operation skill lacks explicit validation/verification checkpoints, and the rubric caps database skills without validation at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single file is well-organized with clear section headers, though the two large SQL blocks could arguably be split into a reference file, matching 'good structure; minor organization gaps'.	4 / 5
	Total	15 / 20 Passed

Description

61%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 and distinctive but lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete trigger phrases and a couple of synonyms would lift it toward the top anchors.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the Slackdump MCP and SQLite MCP are unavailable and you must query slackdump.sqlite via the sqlite3 CLI.'

Add natural synonyms users might say, such as 'Slack export', 'search Slack messages', or 'slackdump.sqlite'.

Optionally list 1-2 more concrete actions (e.g. 'inspect schema, extract JSON payloads') to broaden specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('querying a Slackdump SQLite3 database directly via the sqlite3 CLI') but does not enumerate multiple actions, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Clearly states 'what' (query the Slackdump SQLite DB via sqlite3 CLI) but provides no explicit 'Use when...' trigger clause, so per the rubric guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user with this need would say ('querying', 'Slackdump', 'SQLite3 database', 'sqlite3 CLI'), though it lacks common synonyms/variations, fitting 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	The Slackdump-schema + CLI-fallback scoping gives it a clear niche with only minor overlap with a generic SQLite skill, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rusq/slackdump
Path: cmd/slackdump/internal/mcp/assets/skills/slackdump-sqlite3/SKILL.md
Commit: 00e178d

Reviewed: about 24 hours 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.