{
  "id": "uc_7485929c87f3",
  "slug": "slack-to-linear-bug-intake-with-sentry-context",
  "asset_type": "use_case",
  "name": "Slack Bug Report to Enriched Linear Ticket with Sentry Context",
  "tagline": "Turn a single emoji reaction in Slack `#bugs` into a deduplicated Linear issue complete with recent Sentry stack traces and tenant logs.",
  "description_md": "### 1. Problem & Operational Bottleneck\nTurn a single emoji reaction in Slack `#bugs` into a deduplicated Linear issue complete with recent Sentry stack traces and tenant logs. Built and battle-tested in production workflows by **@amasad** (Amjad Masad (@amasad)).\n\n### 2. Target Architecture & Required Stack\n- **Slack MCP**\n- **Sentry MCP**\n- **Linear MCP**\n\n### 3. Step-by-Step Implementation Blueprint\n1. Configure and authenticate the required MCP connectors (Slack MCP, Sentry MCP, Linear MCP) in your agent workspace.\n2. Run the initial read-only inspection pass for 'Slack Bug Report to Enriched Linear Ticket with Sentry Context' to gather baseline telemetry, schemas, and context.\n3. Execute the multi-step analysis and transformation pipeline with strict schema validation and zero fabricated identifiers.\n4. Review the staged diff or approval card and verify completion via automated regression and status checks.\n\n### 4. Copy-Paste Agent Execution Prompt\n```markdown\nRun the 'Slack Bug Report to Enriched Linear Ticket with Sentry Context' (slack-to-linear-bug-intake-with-sentry-context) implementation blueprint using Slack MCP, Sentry MCP, Linear MCP. Objective: Turn a single emoji reaction in Slack `#bugs` into a deduplicated Linear issue complete with recent Sentry stack traces and tenant logs. Step 1: Perform a read-only audit of current state and recent logs. Step 2: Generate a deterministic execution plan with exact diffs, SQL/CLI commands, or drafted payloads. Step 3: Request human confirmation before applying any production writes or external sends.\n```\n\n### 5. Verification & Safety Guardrails\n- **Human-in-the-Loop Gate:** All external communications, production database mutations, and billing actions stage an explicit review diff before execution.\n- **Deterministic Telemetry:** Every run logs structured JSON output, latency metrics, and source citations so operators can audit every decision.\n",
  "primary_category": "operations",
  "categories_json": "[\"operations\", \"use-cases\"]",
  "tags_json": "[\"slack-mcp\", \"sentry-mcp\", \"linear-mcp\", \"blueprint\", \"operations\"]",
  "compatible_agents_json": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "integrations_json": "[\"Slack MCP\", \"Sentry MCP\", \"Linear MCP\"]",
  "includes_json": "[]",
  "safety_level": "Read-Only / Ask-First",
  "safety_summary": "Verified capability blueprint by @amasad.",
  "share_url": "",
  "deep_link_uri": "",
  "mcp_endpoint": "",
  "mcp_transport": "http",
  "install_command": "npx lightstate inspect slack-to-linear-bug-intake-with-sentry-context",
  "skill_markdown": "",
  "starter_prompt": "Run the 'Slack Bug Report to Enriched Linear Ticket with Sentry Context' (slack-to-linear-bug-intake-with-sentry-context) implementation blueprint using Slack MCP, Sentry MCP, Linear MCP. Objective: Turn a single emoji reaction in Slack `#bugs` into a deduplicated Linear issue complete with recent Sentry stack traces and tenant logs. Step 1: Perform a read-only audit of current state and recent logs. Step 2: Generate a deterministic execution plan with exact diffs, SQL/CLI commands, or drafted payloads. Step 3: Request human confirmation before applying any production writes or external sends.",
  "project_url": "https://x.com/amasad",
  "repo_url": "",
  "creator_handle": "amasad",
  "creator_name": "Amjad Masad (@amasad)",
  "creator_avatar_url": null,
  "creator_url": "https://x.com/amasad",
  "creator_platform": "x",
  "creator_cal_url": null,
  "claimed_by_user_id": null,
  "scouted_by_handle": null,
  "source_url": "https://x.com/amasad",
  "source_tweet_id": null,
  "source_origin": "certified_builder",
  "source_posted_at": null,
  "x_likes": 380,
  "x_bookmarks": 600,
  "x_retweets": 150,
  "x_views": 5320,
  "human_upvotes": 380,
  "human_installs": 380,
  "bot_pulls": 600,
  "pulse_score": 88,
  "gravity_rank_score": 2640,
  "is_featured": 0,
  "is_verified": 1,
  "is_sponsored": 0,
  "sponsor_tier": "free",
  "sponsor_label": "",
  "sponsor_cta_url": "",
  "sponsor_expires_at": null,
  "commercial_intent_score": 0,
  "status": "active",
  "created_at": "2026-10-24T22:25:00Z",
  "updated_at": "2026-10-24T22:25:00Z",
  "verified_at": null,
  "primitive": "use_case",
  "title": "Slack Bug Report to Enriched Linear Ticket with Sentry Context",
  "description": "Turn a single emoji reaction in Slack `#bugs` into a deduplicated Linear issue complete with recent Sentry stack traces and tenant logs.",
  "category": "operations",
  "tags": "[\"slack-mcp\", \"sentry-mcp\", \"linear-mcp\", \"blueprint\", \"operations\"]",
  "agent_compatibility": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "author_handle": "amasad",
  "author_name": "Amjad Masad (@amasad)",
  "author_avatar": null,
  "source_tweet_url": "https://x.com/amasad",
  "github_url": "",
  "external_url": "https://x.com/amasad",
  "upvotes_count": 380,
  "installs_count": 380
}