deepline-feedback

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.

36,137
installs: 0 up / 0 down, score 0.00
votes
Updated: less than a month ago
In the catalog since: 30 Sept 2026
From: code.deepline.com

Get it through your agent

Skill instructions

Rendered from the published SKILL.md, 15 lines.

deepline-feedback (retired)

Quick Start

npm install -g deepline
deepline -h

This skill holds no instructions and will be removed.

deepline feedback send --help explains when to report feedback or product friction, what evidence to include, and the flags.
deepline sessions send --help explains sharing a session transcript and how to rate it.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "deepline-feedback"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Listing on skills.sh

From code.deepline.com via skills.sh

Related skills

deepline-quickstart
Run a quick Deepline demo with a maintained Play.
35,899 installs
niche-signal-discovery
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.
36,239 installs
qa
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
198,679 installs
convex-improve-convex-plugin
Send this coding session's transcript to the Convex team for an AI post-mortem that improves the quickstart system. Run only when the user explicitly asks.
32,640 installs
reproduce-bug-report
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence (a screen recording by default), and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
26,759 installs

More from code.deepline.com

niche-signal-discovery
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.
36,239 installs
build-tam
Build a Total Addressable Market list: size the audience, source companies from ICP filters, then find contacts at those companies at scale.
36,234 installs
portfolio-prospecting
Find companies backed by a specific investor or accelerator, then find contacts and build personalized outbound.
36,146 installs
clay-to-deepline
Convert a Clay table configuration into local Deepline scripts. Handles extraction (MCP or script), documentation, action mapping, script generation, and parity validation against Clay ground truth.
36,123 installs
linkedin-url-lookup
Resolve LinkedIn profile URLs from name + company with strict identity validation to avoid false positives.
36,100 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.