CtrlK
BlogDocsLog inGet started
Tessl Logo

slackdump-sqlite3

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

56

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./cmd/slackdump/internal/mcp/assets/skills/slackdump-sqlite3/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is highly actionable with executable SQL and a clear safety guard, but workflow clarity is held back by the absence of result-verification checkpoints, and conciseness suffers slightly from duplicated large CTE examples.

Suggestions

Add a verification checkpoint after running queries, e.g. checking row counts or confirming SESSION/CHUNK scope before interpreting results, to establish a feedback loop.

Factor the shared CTE structure of the channel-history and thread query examples into one parameterized pattern instead of repeating two large blocks.

Briefly note how to confirm read-only mode (e.g. opening with a read-only URI or checking the query plan) as an explicit validation step.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes SQL/SQLite competence, but the two near-identical large CTE blocks for channel vs thread messages repeat most of their structure and could be tightened or factored.

2 / 3

Actionability

It provides concrete tables, pragma/dot-commands, JSON_EXTRACT examples, and copy-paste-ready SQL queries with explicit placeholders, giving fully executable guidance.

3 / 3

Workflow Clarity

A usable sequence (locate DB, read-only guard, pragmas, tables, query patterns) is present with a strong read-only safety guard, but there is no verification checkpoint or feedback loop for confirming query results, which the rubric caps at 2 for database operations.

2 / 3

Progressive Disclosure

No bundle files exist, so the single SKILL.md is appropriately organized into well-labeled sections (key tables, chunk types, thread messages, latest-version queries) with clear navigation and no nested references.

3 / 3

Total

10

/

12

Passed

Description

57%

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 to a clear niche and names the relevant tooling, but it states only one action and omits an explicit 'Use when' trigger, leaving the when-to-use guidance implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the Slackdump MCP and SQLite MCP are unavailable and you need to query Slackdump data via the sqlite3 CLI.'

List a couple of concrete query actions (e.g. 'list channels, read messages, extract thread replies') to lift specificity from one action to multiple.

Include natural user variations such as 'Slack export' or 'Slack archive' alongside 'Slackdump' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Quotes 'querying a Slackdump SQLite3 database directly via the sqlite3 CLI' name the domain and a single concrete action, but only one action is listed rather than the multiple concrete actions the top anchor requires.

2 / 3

Completeness

It clearly states what the skill does (querying the database via sqlite3) but lacks an explicit 'Use when...' trigger clause in the description; per the guidelines a missing trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like 'Slackdump', 'SQLite3', 'sqlite3 CLI', and 'database' appear, but common user variations such as 'Slack export', 'Slack messages', or 'Slack archive' are missing.

2 / 3

Distinctiveness Conflict Risk

The narrow 'Slackdump SQLite3 database' niche with the 'sqlite3 CLI' fallback is clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rusq/slackdump
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.