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

88%

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

Quality

Content

77%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 highly actionable with executable commands and well-sequenced, validated workflows including error-recovery feedback loops. Its main weaknesses are redundancy across overlapping sections and the absence of any bundle files, leaving lengthy reference material inlined in SKILL.md rather than split into one-level-deep references.

Suggestions

De-duplicate the semantic-query payload: keep one canonical example in Semantic Query Contract and reference it from Fastest Metric Path and Examples instead of repeating it.

Move the large 'Deepline Internal Analytics Sources' table and/or the full error catalog into reference files under references/ and link to them, reducing the inline SKILL.md footprint.

Consolidate the Standard Loop and Fastest Metric Path, which cover overlapping steps, into a single primary workflow with a fast-path callout.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational without explaining basics Claude already knows, but the same semantic-query payload appears near-verbatim in three places (Fastest Metric Path, Semantic Query Contract, Examples) and the Standard Loop overlaps the Fastest Metric Path, so it could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands with complete JSON payloads covering common cases (basic metric, grouped metric, reading the semantic layer), plus concrete error patterns and responses.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced (Standard Loop, Fastest Metric Path, Decision Matrix) with explicit validation checkpoints (pilot smallest query, inspect returned SQL) and a feedback loop ('When a semantic query fails, fix... and rerun before claiming an answer') backed by an error-handling table.	5 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and the ~270-line body inlines substantial reference material (the large internal-analytics-sources table, the full semantic-query contract, error catalog) that could live in separate files; section headers provide structure but no one-level-deep references are signaled.	3 / 5
	Total	16 / 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.

The description is strong across all dimensions: it concretely names the domain and actions, lists natural trigger phrases and tool IDs, answers both what and when explicitly, and includes boundary guidance that distinguishes it from the sibling deepline-gtm skill. No meaningful gaps.

Dimension	Reasoning	Score
Specificity	Names the analytics domain and multiple concrete actions plus tool IDs ('query Snowflake', 'analyze pipeline', 'use the semantic layer', 'run a semantic query', 'snowflake_get_semantic_layer / snowflake_run_semantic_query'), giving comprehensive coverage rather than just 1-2 actions.	5 / 5
Completeness	Clearly states what it does ('answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline') and when to use it via concrete trigger phrases, with explicit boundary guidance to skip prospecting/enrichment.	5 / 5
Trigger Term Quality	Explicitly lists natural user phrases ('query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query') plus tool identifiers, covering synonyms and tool names a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Deepline semantic-layer analytics) with distinct triggers and explicit conflict-avoidance guidance ('Skip prospecting, enrichment... use deepline-gtm for those'), minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Path: skills/deepline-analytics/SKILL.md
Commit: 869569c

Reviewed: 2 days 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.