CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-analytics

Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of snowflake_get_semantic_layer / snowflake_run_semantic_query. Skip prospecting, enrichment, contact finding, outbound, or personalization workflows; use deepline-gtm for those.

Quality

91%

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

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

An exceptionally actionable, well-validated operational skill: exact commands, copy-paste payloads, pilot-query checkpoints, and an error-recovery table. Its only real costs are mild redundancy between the Standard Loop and Fastest Metric Path sections and a monolithic single-file structure that could offload reference-grade detail (data-source catalog, query contract) to bundle files.

DimensionReasoningScore

Conciseness

The body is dense Deepline-specific operational knowledge with essentially no teaching of concepts Claude already knows, but has minor trimmable redundancy: 'Fastest Metric Path' overlaps the 'Standard Loop', and the don't-invent-names/re-read-YAML guidance recurs across three sections. Matches 'Efficient; minor instances of over-explanation that could be trimmed' — not 5 due to that repetition and the length of the internal-sources catalog.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: exact CLI invocations with flags ('deepline run snowflake_get_semantic_layer --input ... --json-out ...'), complete JSON payloads, jq/grep pipelines for large YAML, timestamped file naming, and concrete good/bad filter examples. Matches the top anchor with specific examples covering the common cases.

5 / 5

Workflow Clarity

Two clearly numbered sequences with an explicit validation checkpoint ('Pilot the smallest useful query ... cheaply catches missing credentials, missing semantic objects, and warehouse schema drift') and a full feedback loop (error-pattern table mapping each failure to a response, plus 'fix the table/metric/dimension/filter and rerun before claiming an answer'). Operations are read-only queries, so the destructive-cap does not apply; matches the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and the single body is well-sectioned with headers, decision matrices, and tables giving clear navigation. However, ~185 lines of self-contained content (the internal data-source catalog, the semantic-query contract details) could plausibly be split into reference files. Matches 'Good structure; most content is appropriately placed; minor organization gaps' — not 5 since the monolithic file carries reference-grade detail, not 3 since nothing is buried and sections are clearly signaled.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description with excellent trigger coverage, an explicit when-clause with concrete phrases, and clean boundary routing to the sibling deepline-gtm skill. The only weakness is that the 'what' relies on domain enumeration rather than listing the skill's concrete actions (inspect semantic layer, map metrics/dimensions, report definitions).

DimensionReasoningScore

Specificity

The description enumerates many domains ('business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse') but names only 1-2 concrete actions ('answering ... questions with Deepline', 'run a semantic query'); the skill's actual capabilities like semantic-layer inspection and metric-definition reporting are not listed. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — not 4, since several specific actions are not enumerated.

3 / 5

Completeness

Explicitly answers both what ('answering business analytics ... questions with Deepline') and when ('Use this skill when ... Triggers on phrases like ...') with concrete trigger phrases, matching the top anchor. Not 4 because the 'when' clause is fully explicit with specific trigger phrases rather than improvable.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage: 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', plus domain synonyms (RevOps, GTM, funnel, warehouse) and exact tool IDs (snowflake_get_semantic_layer / snowflake_run_semantic_query). Matches the 'comprehensive coverage of natural terms including synonyms' anchor; nothing obvious is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Deepline warehouse/semantic-layer analytics) with an explicit skip clause routing overlapping cases to the sibling skill ('Skip prospecting, enrichment, contact finding, outbound, or personalization workflows; use deepline-gtm for those'). Minimal conflict risk; matches the top anchor.

5 / 5

Total

18

/

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

getaero-io/gtm-eng-skills

Path

skills/deepline-analytics/SKILL.md

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.