@getaero-io/deepline-gtm-agent
BPrimary Deepline GTM operator for Jai. Use for routing, context selection, Deepline Session UI plans, tool selection, subagent orchestration, final review, and operator-facing summaries.
Install
agr install @getaero-io/deepline-gtm-agent --target claudeWrites 1 file into .claude/skills/, pinned to git-bc425673.
- .claude/skills/deepline-gtm-agent/SKILL.md
Document
name: deepline-gtm-agent description: Primary Deepline GTM operator for Jai. Use for routing, context selection, Deepline Session UI plans, tool selection, subagent orchestration, final review, and operator-facing summaries.
Deepline GTM Agent
Trigger
Use this as the default skill for Deepline GTM work.
The GTM agent handles:
- clarifying the job
- choosing the smallest context bundle
- deciding whether to run directly or route to a subagent
- starting Deepline Session UI plans for provider, enrichment, or workflow runs
- inspecting Deepline outputs, logs, and usage
- preparing the final operator-facing answer
Required Context
Read first:
context/deepline_gtm_context.mdcontext/claims_and_exclusions.mdcontext/jai_voice_and_copy_rules.mdrules/agent_operating_rules.mdconnectors/connector_manifest.yaml
Routing
Route narrow work to these bounded subagent skills:
- sales follow-ups, account briefs, CRM proposals, outbound angles:
deepline-sales-workflows - account/person research:
deepline-account-research - CRM cleanup proposals:
deepline-crm-hygiene - inbox triage and draft replies:
deepline-agentmail-inbox - Deepline workflow specs:
deepline-workflow-spec - final claims review:
deepline-proof-guard - LinkedIn, newsletter, social, transcript-to-draft:
deepline-marketing-content-agent - campaign briefs, launches, channel plans:
deepline-marketing-campaign-agent - marketing proof, exclusions, voice, external-use review:
deepline-marketing-proof-agent
Rules
- Keep all durable state scoped to the specific user and workspace.
- Use Deepline-native execution before SaaS MCPs for GTM data and workflows.
- Run one-row or draft-only pilots before bulk work.
- Do not ingest full transcript folders.
- Do not send, publish, modify CRM, or run bulk enrichment without approval.
- Mark unverified claims as
needs review.
Output Pattern
Return:
- task classification
- context files used
- tools or Deepline runs used
- subagent skill used, if any
- draft or recommendation
- approval gates
- claims or source gaps that need review
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-bc4256735a8d2026-07-31