Deepline feedback
10 AI agent skills for Claude Code — waterfall email enrichment, TAM building, signal discovery, job change detection, and outbound automation. Powered by Deepline CLI with 28+ GTM data providers.
npx -y skills add getaero-io/gtm-eng-skills --skill deepline-feedbackAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Send feedback or bug reports to the Deepline team, including session transcript and environment info. Use when the user asks to report a bug, send product feedback, or share the current Claude/Cowork session with Deepline support.
SKILL.md
2.5 KB, as published. Nobody here has run it
Deepline Feedback
Quick Start
npm install -g deepline
# Fallback for secure sandboxes: mkdir -p "$HOME/.local" && npm config set prefix "$HOME/.local" && export PATH="$HOME/.local/bin:$PATH" && npm install -g deepline --registry https://code.deepline.com/api/v2/npm/
deepline auth register --wait auto
deepline auth wait --timeout 120 # completes Cowork/browser approval; no-op if already connected
deepline auth status
deepline -h
CLI resolution
Run deepline when it is available. If the shell reports that command is missing, use <workspace-root>/.deepline/runtime/bin/deepline (or the npm-created .cmd shim on Windows). If neither exists, follow https://code.deepline.com/SKILL.md to set up Deepline.
Send feedback or a bug report to the Deepline team.
Steps
-
Get feedback text. Use the argument if provided (e.g.
/deepline-feedback the waterfall broke). Otherwise ask the user. -
Confirm. Use AskUserQuestion with a question like:
This report will include:
- Your feedback: {feedback text}
- Environment info (auto-collected)
- Current session transcript
Send this feedback?
Options: "Send it" / "Cancel".
-
If confirmed, send the feedback text first:
deepline feedback send "{feedback text}" --json -
Send the session transcript. Try the normal Claude transcript location first:
deepline sessions send --current-session --jsonIf that reports no session files and
~/mnt/.claude/projectsexists, the run is likely in Cowork. Bridge the mounted transcript directory, then retry. If--current-sessionstill cannot resolve a session, send the newest mounted transcript directly:if [ -d "$HOME/mnt/.claude/projects" ]; then mkdir -p "$HOME/.claude" ln -sfn "$HOME/mnt/.claude/projects" "$HOME/.claude/projects" 2>/dev/null || true deepline sessions send --current-session --json || deepline sessions send --file "$(ls -t "$HOME"/mnt/.claude/projects/*/*.jsonl | head -1)" --json fiUse the plural
sessions sendcommand, not the old singular session form. -
Tell the user it was sent. If cancelled, do nothing.