CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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

77%

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

Highly actionable and well-sequenced content with concrete commands, payloads, and validation feedback loops, but it is a single large monolithic file with some payload redundancy across sections and no use of reference files to push detail one level deeper.

Suggestions

Move the Deepline Internal Analytics Sources table and the Custom SQL Knobs / Semantic Query Contract detail into a reference file (e.g. references/internal-sources.md) referenced one level deep from SKILL.md to improve progressive disclosure and reduce the inline token footprint.

Consolidate the repeated semantic-query payload examples: keep one canonical payload in Fastest Metric Path and have Standard Loop and Examples reference it rather than re-deriving the same JSON shape three times.

Tighten the typed-vs-legacy payload discussion in Semantic Query Contract to a single recommended form plus a one-line note that the legacy flat form is accepted, instead of two full JSON blocks.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence (no primers on SQL/JSON/Snowflake), but the ~275-line body repeats the same semantic-query payload shape across Standard Loop, Fastest Metric Path, and Examples, and the typed-vs-legacy payload explanation could be tightened. It earns most of its tokens but could be leaner.

2 / 3

Actionability

Provides fully executable, copy-paste-ready bash commands and exact JSON payloads (e.g. `deepline tools execute snowflake_run_semantic_query --payload '{...}' --json`), plus concrete decision-matrix and error→response mappings, matching the anchor for fully executable guidance.

3 / 3

Workflow Clarity

Standard Loop and Fastest Metric Path are clearly numbered sequences with explicit validation checkpoints (pilot the smallest query to catch missing credentials/objects cheaply, inspect returned SQL, fix-and-rerun before claiming an answer), with a feedback loop for error recovery in the Error Handling table.

3 / 3

Progressive Disclosure

Sections are clearly organized, but no bundle files exist (references/scripts/assets absent) and the entire skill — including the large Internal Analytics Sources table and the detailed Semantic Query Contract — lives inline in one ~275-line file, so content that would benefit from being split into one-level-deep references is not separated.

2 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that names concrete analytics actions, enumerates natural trigger phrases and tool IDs, explicitly states when to use it, and routes adjacent GTM work to a separate skill. It hits all four anchors at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and domains — "answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions" plus "query Snowflake", "analyze pipeline", "total ACV", "break down by quarter" — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ("answering business analytics... questions with Deepline") and when ("Use this skill when...", "Triggers on phrases like...") with an explicit skip/routing clause ("Skip prospecting... use deepline-gtm for those"), matching the anchor for clearly answering both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural phrases users would actually say ("query Snowflake", "analyze pipeline", "total ACV", "break down by quarter", "use the semantic layer", "run a semantic query") plus concrete tool IDs, giving good coverage of natural terms rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Deepline analytics via Snowflake semantic layer) and explicitly disambiguates from the sibling deepline-gtm skill, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getaero-io/gtm-eng-skills
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.