tldr prompt: ban active-orgs ratio in weekly report TL;DR#58
Open
Assaf Hay Eden (AssafHayEden) wants to merge 3 commits into
Open
tldr prompt: ban active-orgs ratio in weekly report TL;DR#58Assaf Hay Eden (AssafHayEden) wants to merge 3 commits into
Assaf Hay Eden (AssafHayEden) wants to merge 3 commits into
Conversation
Manager feedback: "(now 15/18 active)" reads as state, not movement, and distracts from the actual headline. Remove it from the prompt's good example, add an explicit BANNED METRICS section, add a Bad example showing the anti-pattern, and add a STYLE rule preferring movement language over state language.
…add Enterprise Dashboard link Restructures the weekly leadership Slack post so each lead is counted exactly once across the three sections, and surfaces the Hex Enterprise Dashboard as a deep-link from the Studio Enterprise section. Bucketing rule (locked): OSS = OSS PEL only (no PQL flow) API = (API + Both) PQL and (API + Both) PEL Studio = Studio-only PQL and Studio-only PEL SQL: new marketing_pels_by_product CTE on marketing.final_sf_lead_opportunity (lead-level, deduped) classifies PELs as API / Studio / Both / OSS via the ltx_api / ltx_studio flags. Surfaced as J_studio_summary.wow_trends.pels_by_product. Dry-run cost: 545 MB (was 537 MB). render_body.js: drives the new bucketing off pqls_by_product and pels_by_product. The legacy Block G (G_pql_pel) is still emitted by the SQL but no longer rendered so all three sections share one source of truth. Adds a STUDIO_DASHBOARDS array with the Hex Enterprise Dashboard URL; the line is omitted when the array is empty. tldr_system_prompt.md: extends the PEL-skip rule to all three PEL lines and calls out the OSS PEL bucket as especially noisy (sensitive to product-flag tagging gaps), so the LLM does not headline OSS PEL swings. Verified end-to-end: PEL totals reconcile (388 OSS + 51 API+Both + 294 Studio = 733, matches the lead-level table). Co-authored-by: Cursor <cursoragent@cursor.com>
5 tasks
…rt-leads-regroup-and-dashboards leadership-report: split PQL/PEL into OSS / API / Studio buckets and add Enterprise Dashboard link
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Manager feedback on the first TL;DR run: "(now 15/18 active)" reads as a state metric, not a movement, and dilutes the actual headline.
The original prompt actively encouraged this — the big-news "Good" example literally taught the model to write "pushing Studio to 14 of 16 contract orgs active". This PR fixes that.
Changes to
agents/reports/ltx-leadership-weekly-report/n8n/tldr_system_prompt.md:BANNED METRICSblock under SELECTION RULES, banning:"15/18 active","14 of 16 contract orgs active")The body (
render_body.js) still surfaces active orgs as a bullet — that's where state metrics belong. Only the TL;DR is constrained.Test plan
Made with Cursor