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

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

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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: thoughtleaders-cli
-Version: 0.6.41
+Version: 0.6.42
 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
@@ -30,6 +30,15 @@ Description-Content-Type: text/markdown
 
 ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence from the terminal.
 
+## Requirements
+
+- Python 3.12+
+- [jq](https://stedolan.github.io/jq/)
+- [ripgrep](https://github.com/BurntSushi/ripgrep)
+- [duckdb](https://duckdb.org/)
+
+For automated installs on MacOS, prefer installing Homebrew and use the pipx package manager, but ask the user if they have the admin access (sudo) password first. If not, proceed by using `uv` and installing everything locally.
+
 ## Install
 
 ### As a developer
@@ -168,13 +177,6 @@ the pool of Proposals is yet smaller, and the pool of Deals is the smallest.
 
 # Integrations
 
-## Requirements
-
-- Python 3.12+
-- [jq](https://stedolan.github.io/jq/)
-- [ripgrep](https://github.com/BurntSushi/ripgrep)
-- [duckdb](https://duckdb.org/)
-
 ## Claude Code Integration
 
 If you use Claude Code, install the plugin for natural language access:

{thoughtleaders_cli-0.6.41 → thoughtleaders_cli-0.6.42}/README.md

@@ -2,6 +2,15 @@
 
 ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence from the terminal.
 
+## Requirements
+
+- Python 3.12+
+- [jq](https://stedolan.github.io/jq/)
+- [ripgrep](https://github.com/BurntSushi/ripgrep)
+- [duckdb](https://duckdb.org/)
+
+For automated installs on MacOS, prefer installing Homebrew and use the pipx package manager, but ask the user if they have the admin access (sudo) password first. If not, proceed by using `uv` and installing everything locally.
+
 ## Install
 
 ### As a developer
@@ -140,13 +149,6 @@ the pool of Proposals is yet smaller, and the pool of Deals is the smallest.
 
 # Integrations
 
-## Requirements
-
-- Python 3.12+
-- [jq](https://stedolan.github.io/jq/)
-- [ripgrep](https://github.com/BurntSushi/ripgrep)
-- [duckdb](https://duckdb.org/)
-
 ## Claude Code Integration
 
 If you use Claude Code, install the plugin for natural language access:

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

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

{thoughtleaders_cli-0.6.41 → thoughtleaders_cli-0.6.42}/skills/tl/SKILL.md

@@ -1,13 +1,7 @@
 ---
 name: tl
 description: |
-  Query and analyze ThoughtLeaders business data using the `tl` CLI. Default to raw database queries via `tl db pg|fb|es` for anything non-trivial (joins, aggregations, multi-condition filters, anything that would otherwise need post-processing); use the structured resource commands (sponsorships, deals, channels, brands, uploads, snapshots, reports) only for trivially simple lookups (single-record show by ID, plain filtered lists). You ARE the AI layer — do not use `tl ask`.
-
-  **Use this skill for ANALYTICAL questions**: counts, metrics, trends, time-series, distributions, single-record drill-downs, revenue / pipeline-weighting math, view-curve analysis, cross-source business questions. *"How many deals did we close last quarter?"*, *"What's the weighted pipeline by sales owner?"*, *"Show me the view curve for video X"*, *"Find mentions of Surfshark in transcripts"*, *"Investigate this video"*.
-
-  **DEFER to `tl-cli:tl-report-builder`** when the user wants a **LIST of entities with filters** — channels, videos, brands, or sponsorships shaped as a report deliverable, regardless of whether they say "report" or "campaign". *"Show me partnerships from last quarter for beauty creators"*, *"Find me gaming channels with 100K+ subs"*, *"List the brands flagged as Managed Services"*, *"All sponsorships for channel X"*, *"Build me a TPP fintech list"* — every one of these goes to `tl-cli:tl-report-builder`, not here. The report-builder owns the four report types (content / brands / channels / sponsorships) and the preview/save flow; using this skill instead produces ad-hoc data dumps that bypass the saved-report system.
-
-  Quick routing test: *"would the answer to this prompt be a TL report (a list of entities I'd want to come back to)?"* — if yes, route to `tl-cli:tl-report-builder`. If no (it's a number, a chart, a single record, or an exploratory analysis), use this skill.
+  Query and analyze ThoughtLeaders business data using the `tl` CLI. Default to raw database queries via `tl db pg|fb|es` for anything non-trivial (joins, aggregations, multi-condition filters, anything that would otherwise need post-processing).  Use this skill for ANALYTICAL questions about channels, brands and sponsorships: counts, metrics, trends, time-series, distributions, single-record drill-downs, revenue / pipeline-weighting math, view-curve analysis, cross-source business questions. Examples: "How many deals did we close last quarter?", "What's the weighted pipeline by sales owner?", "Show me the view curve for video X", "Find mentions of Surfshark in transcripts", "Investigate this video".
 ---
 
 # ThoughtLeaders Data Analyst
@@ -378,6 +372,8 @@ tl db pg "SELECT b.name, COUNT(*) AS deals
 
 See [references/postgres-schema.md](references/postgres-schema.md) for the accepted-SQL rules and the table/column catalogue. `tl schema pg` prints the live table/column listing visible to the caller.
 
+**PG cost is per-query.** The credit rate for a `tl db pg` call equals a base rate plus a surcharge for every priced table referenced and every priced column referenced (additive on both sides). Most tables and columns carry no surcharge; sensitive ones (e.g. demographics, channel outreach emails) cost more. Run `tl describe show db --json` to see the live surcharge map, and check `usage.credit_rate` in the response envelope after a query to see what your query was actually charged.
+
 ### Three sources, each authoritative for different things
 
 - **Postgres** — deals, pipeline, brands, channels, users, organizations, profiles, revenue. Source of truth for deal state. Reachable via the structured `tl` commands or raw `tl db pg`.