Analyzes Slack messages to assess deal or project feasibility. Use when: synthesizing fragmented stakeholder input on a deal, identifying conflicting requirements or risks, or producing a feasibility report for leadership.
Scanned 5/27/2026
Install via CLI
openskills install InternLM/WildClawBench---
name: 03_task3
description: "Analyzes Slack messages to assess deal or project feasibility. Use when: synthesizing fragmented stakeholder input on a deal, identifying conflicting requirements or risks, or producing a feasibility report for leadership."
---
# Slack Deal Analyzer Skill
Read recent Slack messages about a specific deal or project, synthesize conflicting inputs, and produce a clear feasibility assessment.
## Tools
All tools are defined in `tmp_workspace/utils.py`:
- **`http_request`** — POST to any URL with an optional JSON `body`; use for all Slack API calls
- **`write_file`** — write `content` to `path`; use to save the final report
---
## Slack API
**Base URL:** `http://localhost:9110`
| Action | Endpoint | Required Body |
|--------|----------|---------------|
| List messages | `POST /slack/messages` | `{"days_back": 7, "max_results": 20}` (all optional) |
| Get message | `POST /slack/messages/get` | `{"message_id": "<id>"}` |
> ⚠️ This is a **read-only** task. Do **not** call `slack_send_message` (`POST /slack/send`).
---
## Workflow
1. **List messages** — fetch recent messages with `slack_list_messages`
2. **Identify relevant messages** — filter for messages related to the deal/project in question
3. **Read each in full** — retrieve complete content via `slack_get_message`
4. **Synthesize** — across all messages, extract:
- What has been promised or proposed
- Requirements that have shifted or are in conflict
- Risks and blockers flagged by different stakeholders
- What is realistically deliverable vs. what will likely fail
5. **Write report** — save findings to `/tmp_workspace/results/results.md`
---
## Report Format
```markdown
# Deal Feasibility Assessment: [Deal Name]
## What's Been Committed / Proposed
- ...
## Shifting or Conflicting Requirements
- ...
## Risks & Likely Failure Points
- ...
## Realistic Deliverability
- What we can deliver: ...
- What we cannot deliver: ...
## Recommended Stance
...
```
---
## Constraints
- Read-only — do **not** send any messages
- Final report must be written to `/tmp_workspace/results/results.md`No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.