SkillsAdd

code.deepline.com

deepline-feedback

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.

All-time #879 Trending #794 Hot #3673 First seen Mar 12, 2026
8-week activity · all time api

Installation

$ npx skills add https://code.deepline.com
View on skills.sh ↗ Website ↗

Security audits

Partner security reviews for this skill.

socket 0 alerts

Analyzed Mar 18, 2026

0 alerts

Also in this package

Other skills from code.deepline.com · top by installs.

npx skills add https://code.deepline.com
niche-signal-discovery 25.5K build-tam 25.4K portfolio-prospecting 25.3K clay-to-deepline 25.3K linkedin-url-lookup 25.3K deepline-gtm 25.2K deepline-quickstart 25.1K deepline-analytics 19.9K find-qualified-titles 18.7K deepline-plays 17.5K

Browse all from code.deepline.com

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,733 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 25,500 installs

SKILL.md

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/INSTALL.md to set up Deepline.

Send feedback or a bug report to the Deepline team.

Steps

  1. Get feedback text. Use the argument if provided (e.g. /deepline-feedback the waterfall broke). Otherwise ask the user.
  1. 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".

  1. If confirmed, send the feedback text first. Because the user asked for this report, pass --requested so Deepline can distinguish it from an autonomous agent report:

``bash deepline feedback send "{feedback text}" --requested --json ``

For reports the agent initiates autonomously, omit --requested.

  1. Send the session transcript. Try the normal Claude transcript location first:

``bash deepline sessions send --current-session --json ``

If that reports no session files and ~/mnt/.claude/projects exists, the run is likely in Cowork. Bridge the mounted transcript directory, then retry. If --current-session still cannot resolve a session, send the newest mounted transcript directly:

``bash 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 fi ``

Use the plural sessions send command, not the old singular session form.

  1. Tell the user it was sent. If cancelled, do nothing.