MetatroncubeSoftwareSolutions/quorlasocial
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Runs: tell the AI the dashboard exports PDFs after the run

Browse Source 
Stops summaries that tell the team to export PDFs or delete .data.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
metatroncubeswdev 2026-10-28 00:23:12 -04:00
parent c8ed9870d0
commit 6317d89be0
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.claude/skills/competitor-scan/SKILL.md
View File

@ -37,6 +37,6 @@ Goal: tell the client who they're actually up against, who's winning and *why*,
Order: Summary (3 sentences: where the client stands, who's leading and why, the biggest opening) → `mc:rivals` → `mc:rivals-map` → **Who's winning and why** (one `> [!NOTE]` per top 2–3 rivals: what they do that works) → `mc:rivals-formats` → `mc:rivals-posts` → `mc:rivals-tags` → `mc:rivals-google` if local → **Openings nobody owns** (`> [!WIN]` per gap, 3–5) → **What we'll do** (`mc:actions`, 5 items, owner + when) → **Who to track** (list the suggested accounts and say the team will confirm them).
Never copy a rival's content or suggest misleading comparisons; learn the pattern, not the post.
6. Export the PDF: `node tools/report-pdf/build.mjs clients/<slug>/competitors-YYYY-MM.md`. Append 1–2 dated lessons to `history.md`.
6. Export the PDF: `node tools/report-pdf/build.mjs clients/<slug>/competitors-YYYY-MM.md` (from the dashboard, skip this: the dashboard exports it after the run). Append 1–2 dated lessons to `history.md`.
7. Final message: the PDF path, how many accounts were suggested vs skipped, and a reminder that someone must add or dismiss the suggestions on the Competitors page so they're tracked from now on.

2
dashboard/server/jobs.js
View File

@ -32,7 +32,7 @@ Plan all of ${month}, not just next week: every week that starts in ${month}, on
const HEADLESS_RULES = `You are running headlessly from the agency dashboard. Nobody can answer questions mid-run.
- Don't stop to ask. Make sensible assumptions, finish the job, and list open questions for the team inside the files you write (and in your final message).
- Never publish, schedule or post anything, and never create or change records in Odoo from this run.
- Only write inside clients/, team/ and reports/. Export finished client-facing reports to PDF with the project's PDF builder.
- Only write inside clients/, team/ and reports/. Don't export PDFs or run Bash: when the run ends, the dashboard exports every changed report to PDF with fresh chart numbers. Never tell the team to export a PDF or delete .data.json files.
- End with a short summary: what you produced (file paths) and anything the team must check.`;
const READ_TOOLS = [