deepline-plays-feedback
Send Deepline SDK/V2 CLI feedback or bug reports, including environment info and the current Claude/Cowork session transcript. Use when the user asks to report a Deepline bug, share a failing run, or send feedback from a V2 SDK workflow.
- Installs
- 237
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://code.deepline.com --skill deepline-plays-feedback- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads deepline-plays-feedback automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Deepline Plays Feedback
Send feedback or a bug report to Deepline support from the V2 SDK CLI.
Steps
-
Get feedback text. Use the argument if provided, such as
/deepline-plays-feedback plays run failed after upload. Otherwise ask the user for the message to send. -
Confirm. Ask before sending because the report includes the feedback text, environment info collected by the CLI, and a session transcript. If the user cancels, stop.
-
Send the feedback text. The V2 SDK command is
feedback send; the text is positional: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 fi -
Avoid stale command shapes. Do not use the legacy
provide-feedbackcommand, a--textflag for feedback, or the old singular session form; those target older or unsupported CLI surfaces. -
Tell the user it was sent.
FAQ
What does the deepline-plays-feedback skill do?
Send Deepline SDK/V2 CLI feedback or bug reports, including environment info and the current Claude/Cowork session transcript. Use when the user asks to report a Deepline bug, share a failing run, or send feedback from a V2 SDK workflow.
How do I install deepline-plays-feedback?
Run npx skills add https://code.deepline.com --skill deepline-plays-feedback in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/deepline-plays-feedback/ (personal) or .claude/skills/deepline-plays-feedback/ (project).
Which AI agents can use deepline-plays-feedback?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is deepline-plays-feedback safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains deepline-plays-feedback?
It is published by code.deepline.com in code.deepline.com. It has 237 recorded installs.
More from code.deepline.com
niche-signal-discovery
code.deepline.com
Deprecated alias. This skill was renamed to deepline-scoring. Use when a user or script still invokes /niche-signal-discovery: immediately load and follow the deepline-scoring skill instead. Triggers: ICP analysis, niche signals, won vs lost analysis, differential signals, signal discovery, ICP signal report, account scoring signals, lead scoring, first-party signals, buyer signals.
build-tam
code.deepline.com
Build a Total Addressable Market list: size the audience, source companies from ICP filters, then find contacts at those companies at scale.
portfolio-prospecting
code.deepline.com
Find companies backed by a specific investor or accelerator, then find contacts and build personalized outbound.
deepline-feedback
code.deepline.com
Retired. Reporting feedback and sharing a session are documented by the CLI itself: run deepline feedback send --help and deepline sessions send --help. Kept only so installed CLIs that still list this skill keep syncing.
clay-to-deepline
code.deepline.com
Convert a Clay table, or a whole Clay workspace via the Clay CLI, into Deepline plays. Handles extraction, documentation, action mapping, play generation, and cell-level parity validation against Clay ground truth.
linkedin-url-lookup
code.deepline.com
Retired. LinkedIn URL lookup is part of deepline-gtm. Kept only so installed CLIs that still list this skill keep syncing.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.