thoughtleaders-cli 0.6.42__tar.gz → 0.6.43__tar.gz

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tl-cli",
-  "version": "0.6.42",
+  "version": "0.6.43",
   "description": "ThoughtLeaders CLI — query sponsorship deals, channels, brands, uploads, and intelligence from the terminal",
   "author": {
     "name": "ThoughtLeaders",

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: thoughtleaders-cli
-Version: 0.6.42
+Version: 0.6.43
 Summary: ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence
 Project-URL: Homepage, https://thoughtleaders.io
 Project-URL: Repository, https://github.com/ThoughtLeaders-io/thoughtleaders-cli

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "thoughtleaders-cli"
-version = "0.6.42"
+version = "0.6.43"
 description = "ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence"
 readme = "README.md"
 license = "MIT"

thoughtleaders_cli-0.6.43/skills/tl-feedback/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: tl-feedback
+description: Compose and submit feedback about the current AI Agent session that used the `tl` CLI. Triggers on phrases like "send feedback", "report a problem with the session", "tell the team how this went", "submit session feedback", "feedback about tl", "this session was frustrating, send feedback", "tl feedback", "share this session with the team", "log issues from this run". Use it ONLY when the user wants to send a written report about the session to the ThoughtLeaders team — never on requests that just *use* `tl` to query data.
+---
+
+# Send a session-feedback report via `tl feedback`
+
+The `tl feedback` command POSTs a markdown-formatted message to the ThoughtLeaders team's `#ai-feedback` Slack channel. The server-side endpoint prepends the user/org context (user, email, organisation, links into Django admin), so the body you send should contain **only the session-specific report** — do not try to restate the user's name or org yourself.
+
+This skill produces that body. Do not invoke `tl feedback` until every section below is written.
+
+## When to invoke
+
+Trigger this skill **only** when the user is explicitly asking for feedback to be sent — phrases like "send feedback", "log a problem with this session", "share these issues with the team", "submit session feedback", "tl feedback". Do **not** trigger it when the user is asking `tl` to fetch data, build a report, or perform any other analytical task; in those cases the `tl-cli:tl` or `tl-cli:tl-report-builder` skills are the right ones.
+
+If you are not sure whether the user wants the feedback sent now or is just venting, ask one clarifying question before composing the body. Otherwise proceed.
+
+## What the body must contain
+
+Write the body to a scratch buffer (do not stream it directly to the shell) and only send it once all four sections are present. Use the **Slack mrkdwn subset** of markdown — Slack does not render standard markdown:
+
+| Want | Slack mrkdwn |
+| --- | --- |
+| Bold | `*bold*` (single asterisk) |
+| Italic | `_italic_` |
+| Strike | `~strike~` |
+| Inline code | `` `code` `` |
+| Code block | triple backticks |
+| Block quote | `> text` |
+| Bullets | leading `• ` (or `- `) |
+| Link | `<https://example.com|label>` |
+
+`**double-asterisk bold**`, `[text](url)` links, and `#` headers render as **plain characters** in Slack — do not use them.
+
+### Required sections, in this exact order
+
+1. **One-sentence summary of the session.**
+   Lead with one sentence (no header, no bullets) describing what the user was trying to accomplish in this session and how it went overall (e.g. *"Pulled Q1 sponsored-channel rosters for three brands; ran into a sanitizer rejection on the third query and resolved it via `tl db pg`."*).
+
+2. **User prompts and the work done.**
+   Section header `*User prompts and actions taken*`. Then a bulleted list — one bullet per distinct prompt the user issued in the session, in order. Each prompt is the parent bullet (a short paraphrase of what they asked, in quotes). Under each prompt, indent sub-bullets listing every concrete tool call or shell command you ran to handle it. Examples:
+
+   ```
+   • _"Find me Holafly's sponsored channels in the last 6 months"_
+       • `tl db pg "SELECT DISTINCT c.id, c.channel_name FROM …"`
+       • `tl brands find Holafly`
+   • _"Now show their evergreenness scores"_
+       • `tl db es '{"aggs":{"channels":{"terms":{"field":"channel.id"}}}}'`
+       • `tl db pg "SELECT id, channel_name, evergreenness FROM thoughtleaders_channel WHERE id IN (…)"`
+   ```
+
+   Include every prompt — even ones that were short clarifications. If you used a non-`tl` tool (`jq`, `duckdb`, Read, Edit, Bash), list it too. Do not dump full command output; one line per command is enough.
+
+3. **Analysis section.**
+   Section header `*Analysis: problems, frustrations, weaknesses*`. Write a few short paragraphs (no bullets needed) covering, in this order:
+   - **Problems / data errors** encountered (e.g. sanitizer rejections, schema mismatches, missing fields, wrong field names, 5xx responses, slow endpoints). Quote the exact error text or command when relevant.
+   - **User frustrations** signalled in their messages (impatience, asking the same question twice, "this isn't what I asked for", profanity, abandoning a thread). Be honest — the team needs the actual signal, not a sanitised version. Do not editorialise about whether the frustration was justified.
+   - **Weaknesses / gaps in the `tl` CLI or skills** that surfaced. Concrete examples: missing filters, output formats that needed jq post-processing, schema docs that were wrong or out of date, commands that ought to exist but don't, places where you (the agent) had to guess.
+   - **What went well** — keep this short (one or two sentences). Skip the section if nothing notably went well.
+
+   If a category has nothing to report, write *"None observed."* under the heading rather than omitting the heading entirely. Do not invent problems to fill space.
+
+4. **Anything else the user explicitly asked you to include.**
+   If the user's "send feedback" request contained a specific message ("tell them the new find command is great"), append it verbatim under a final `*From the user*` section as a block quote.
+
+## After the body is ready
+
+Send it with `tl feedback` — pass the body as a single argument (heredoc / `$(cat <<EOF …)` works well for multi-line content):
+
+```bash
+tl feedback "$(cat <<'EOF'
+<the body you composed>
+EOF
+)"
+```
+
+On success the CLI prints `Thanks! Your feedback was sent to the team.` Confirm to the user with a brief, neutral one-liner ("Sent."). Do not echo the full body back to the user — they wrote it with you, they don't need to re-read it.
+
+If `tl feedback` exits non-zero (network failure, server error), show the user the raw error and offer to retry. Do not silently swallow failures — feedback that didn't reach Slack is the worst possible outcome here.
+
+## What NOT to do
+
+- Do not prepend user name, email, organisation, or admin links to the body. The server adds those.
+- Do not use `**bold**` or `[text](url)` markdown — Slack will print the literal characters.
+- Do not split the report into multiple `tl feedback` calls. One message, one call.
+- Do not invent prompts or commands you did not actually use. If you can't recall, write *"(earlier commands not captured)"*.
+- Do not mark the task complete until `tl feedback` exits 0.

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/skills/tl-report-builder/SKILL.md

@@ -646,7 +646,7 @@ The view exposes one row per (adlink × brand × channel) and surfaces these col
 - `organization_id`, `organization_name`, `organization_is_managed_services`
 - `adlink_owner_advertiser_email`, `adlink_owner_sales_email`
 
-**Important: count and sample MUST be deduped by `adlink_id`.** The view holds one row per `(adlink × brand × channel)` — a single sponsorship that involves multiple brands or multiple channel relations produces multiple rows. Type-8 reports count sponsorship records (AdLinks), not view rows. **Always use `COUNT(DISTINCT adlink_id)` for `db_count` and dedupe samples by `adlink_id`.** A globally-confirmed 184 view rows correspond to fewer underlying adlinks — direct `COUNT(*)` overcounts those cases.
+**Important: count and sample MUST be deduped by `adlink_id`.** The view holds one row per `(adlink × brand × channel)` — a sponsorship spanning multiple brands or channels produces multiple rows. Type-8 counts sponsorship records (AdLinks), not view rows. **Always `COUNT(DISTINCT adlink_id)` for `db_count`; dedupe samples by `adlink_id`.** Direct `COUNT(*)` overcounts multi-brand/multi-channel adlinks.
 
 ##### Filter predicate mapping (must mirror the saved FilterSet)
 

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/skills/tl-report-builder/references/report_glossary.md

@@ -22,33 +22,31 @@ Phase 1 + 2 disambiguation: report-type synonyms, TL terminology, field-pair cho
 | **"pipeline"** *(no other context)* | Type 8 with active-stage filter | Default to type 8; confirm. |
 | **"book of business"** | Type 8 with `tl_sponsorships_only: true` | Default to type 8 + filter; confirm scope. |
 
-### TL role / pool synonyms
+### TL role / pool synonyms + TL terminology
 
-| Term | Meaning | Where it shows up |
-|---|---|---|
-| **MSN** | Media Selling Network — broad ~11K opted-in channel pool | `msn_channels_only` |
-| **TPP** | ThoughtLeaders Premier Partners — smaller ~169 high-touch managed pool. **Resolve-and-pin pattern**: `SELECT id FROM thoughtleaders_channel WHERE is_tl_channel = TRUE AND is_active = TRUE ORDER BY id` → put IDs in `filterset.channels`. TPP IS a recognized filter; the implementation detail is resolve-and-pin. | `is_tl_channel = TRUE` resolved → `filterset.channels` |
-| **MBN** | Media Buying Network — managed-services advertisers | `cross_references` type `include_sponsored_by_mbn` |
-| **AM** / **Account Manager** | Advertiser-side deal owner | `owner_advertiser_name` (in `filters_json` for type 8) |
-| **TM** / **Talent Manager** / **Publisher Manager** | Publisher-side deal owner | `owner_publisher_name` (in `filters_json` for type 8) |
+> **Canonical source**: [`tl/references/business-glossary.md`](../../tl/references/business-glossary.md) — the canonical home for TL business terminology (MSN, TPP, MBN, AM/TM ownership, View Guarantees, Net revenue, TL profit, performance grade, industry-vs-TL vocabulary translations). Do NOT redefine these terms here; this skill defers to the glossary.
 
-## TL terminology — use these
+Quick **FilterSet-mapping reference** (where these business terms appear in the report-builder context — for full definitions see the canonical glossary):
 
-| Term | Meaning | Where it shows up |
-|---|---|---|
-| **Reach** | TL's rolling audience-size metric (not raw YouTube subs) | `reach_from` / `reach_to` |
-| **Projected Views (PV)** | Pricing estimate for next video; drives sponsorship pricing | `projected_views_from` / `projected_views_to`; column `Projected Views` |
-| **View Guarantee (VG)** | Contractual floor on views for a deal. Type-8 only. | Type 8 columns: `Views Guaranteed`, `Views Guarantee Days` |
-| **Net revenue** | TL's earned revenue. NOT "margin." | Type 8 column: `Revenue` |
-| **TL profit** | `Price - Cost`. NOT "margin." | Custom formula `{Price} - {Cost}` |
-| **Sold sponsorship** | Contractually agreed deal | Type 8 `filters_json.publish_status` |
-| **Match / Proposal / Deal** | Funnel: Match (possible) → Proposal (offered) → Deal (sold) | `filters_json.publish_status` for type 8 |
+| Term | FilterSet / `filters_json` mapping in this skill |
+|---|---|
+| **MSN** | `msn_channels_only: true` |
+| **TPP** | resolve-and-pin pattern — `SELECT id FROM thoughtleaders_channel WHERE is_tl_channel = TRUE AND is_active = TRUE ORDER BY id` → put IDs in `filterset.channels` |
+| **MBN** | `cross_references` type `include_sponsored_by_mbn` |
+| **AM** / Account Manager | `owner_advertiser_name` (in `filters_json` for type 8) |
+| **TM** / Talent Manager | `owner_publisher_name` (in `filters_json` for type 8) |
+| **Reach** | `reach_from` / `reach_to` (narrate as "subscribers" per business-glossary) |
+| **Projected Views (PV)** | `projected_views_from` / `projected_views_to`; column `Projected Views` |
+| **View Guarantee (VG)** | Type 8 columns: `Views Guaranteed`, `Views Guarantee Days` |
+| **Net revenue** | Type 8 column: `Revenue` |
+| **TL profit** | Custom formula `{Price} - {Cost}` (NOT "margin" — see glossary) |
+| **Sold sponsorship / Match / Proposal / Deal** | `filters_json.publish_status` (see "Deal-stage jargon" below for ID mapping) |
 
-## TL terminology — DON'T use
+### Industry terms — DON'T emit in config
 
 Industry-default terms that don't translate; never put in field names, formulas, columns, or user-facing copy:
 
-- ❌ **"flight"** (MarTech) → say "campaign" or "date range"
+- ❌ **"flight"** (MarTech) → say "campaign" or "date range" (full flight-variant translation lives in [`business-glossary.md`](../../tl/references/business-glossary.md) "Industry Terms vs TL Vocabulary")
 - ❌ **"hero / hero-tier / hero channel"** → say "high-priority" or "TPP" if appropriate
 - ❌ **"margin"** (accounting) → say `Net revenue` or `TL profit`
 - ❌ **"impressions"** in YouTube context → say `Views` or `Projected Views`
@@ -71,7 +69,7 @@ Map informal descriptions → `filters_json.publish_status` IDs (integer; platfo
 | **"in progress"** / **"active"** | `0, 2, 3, 6` | — | Active incl. sold |
 | **"live"** / **"currently running"** | `3` | `ad_publish_status: "0"` | Sold AND published |
 
-Status reference: `0` Creator Approved, `1` Unavailable, `2` Pending, `3` Sold, `4` Rejected by Brand, `5` Rejected by Creator, `6` Proposal Approved, `7` Matched, `8` Reached Out, `9` Rejected by Agency.
+Full `publish_status` enum (all 12 codes incl. CLIENT_SIDE_* and pipeline weights) lives at the canonical schema home: [`tl/references/postgres-schema.md` → `publish_status` Constants](../../tl/references/postgres-schema.md#publish_status-constants). The NL → ID mapping above is what this skill consumes; refer to the schema doc for the full enum and Django-side constants.
 
 ## Field-pair disambiguation
 

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/src/tl_cli/__init__.py

@@ -1,3 +1,3 @@
 """ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence."""
 
-__version__ = "0.6.42"
+__version__ = "0.6.43"

thoughtleaders_cli-0.6.43/src/tl_cli/commands/feedback.py

@@ -0,0 +1,61 @@
+"""tl feedback — Send a markdown-formatted note to the #ai-feedback channel."""
+
+import sys
+
+import typer
+from rich.console import Console
+
+from tl_cli.client.errors import ApiError, handle_api_error
+from tl_cli.client.http import get_client
+
+
+app = typer.Typer(help="Send feedback about the CLI to the team (free)")
+console = Console(stderr=True)
+
+
+@app.callback(invoke_without_command=True)
+def feedback(
+    ctx: typer.Context,
+    text: str = typer.Argument(
+        None,
+        help='Markdown-formatted feedback. Omit to read from stdin (handy for piping or heredocs).',
+    ),
+) -> None:
+    """Send a markdown-formatted note to the ThoughtLeaders team.
+
+    The server prepends your user/org context and posts everything to the
+    #ai-feedback Slack channel. Slack supports a subset of markdown —
+    `*bold*`, `_italic_`, `~strike~`, ``code``, ```fences```, `> quotes`,
+    and `<url|label>` links. Standard `**bold**`, `[text](url)` links,
+    and `#` headers render as plain text in Slack.
+
+    Examples:
+        tl feedback "The new *find* command is great, but it should also accept channel IDs from URLs."
+        echo "long note here" | tl feedback
+        tl feedback <<< "$(cat note.md)"
+    """
+    if ctx.invoked_subcommand is not None:
+        return
+
+    body = text
+    if body is None:
+        if sys.stdin.isatty():
+            console.print('[red]Error:[/red] no feedback text provided.')
+            console.print('Pass the text as an argument, or pipe it via stdin.')
+            raise typer.Exit(1)
+        body = sys.stdin.read()
+
+    body = (body or '').strip()
+    if not body:
+        console.print('[red]Error:[/red] feedback text is empty.')
+        raise typer.Exit(1)
+
+    client = get_client()
+    try:
+        client.post('/feedback', json_body={'text': body})
+    except ApiError as e:
+        handle_api_error(e)
+    finally:
+        client.close()
+
+    console.print('[green]Thanks![/green] Your feedback was sent to the team.')

{thoughtleaders_cli-0.6.42 → thoughtleaders_cli-0.6.43}/src/tl_cli/main.py

@@ -28,6 +28,7 @@ from tl_cli.commands.sponsorships import app as sponsorships_app
 from tl_cli.commands.describe import app as describe_app
 from tl_cli.commands.schema import app as schema_app
 from tl_cli.commands.doctor import app as doctor_app
+from tl_cli.commands.feedback import app as feedback_app
 from tl_cli.commands.reports import app as reports_app
 from tl_cli.commands.setup import app as setup_app
 from tl_cli.commands.snapshots import app as snapshots_app
@@ -108,6 +109,7 @@ app.add_typer(balance_app, name="balance")
 app.add_typer(credits_app, name="credits")
 app.add_typer(doctor_app, name="doctor")
 app.add_typer(whoami_app, name="whoami")
+app.add_typer(feedback_app, name="feedback")
 
 # `changelog` is a single command (not a sub-typer) so positional version args
 # don't get interpreted as subcommand names.