molecule-ai/molecule-ai-org-template-molecule-dev
34
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
d7758fd11b
molecule-ai-org-template-mo.../content-marketer/idle-prompt.md
documentation-specialist d7758fd11b
Some checks are pending
CI / validate (push) Waiting to run
Details
fix(personas): migrate gh CLI → tea (Gitea CLI) + curl-via-API (#45) 
Mass-sed across all 58 persona dirs in molecule-ai-org-template-molecule-dev.

Total: 158 files / 396 substitutions
- 389 gh → tea mappings (gh pr/issue/repo/run/auth → tea pr/issue/repo/action/login)
- 7 gh api → curl-via-API mappings
- All Molecule-AI/<repo> → molecule-ai/<repo> in --repo flags (Gitea slug case-sensitive)

Plus SHARED_RULES.md migration callout block + tea install snippet:
- Tea v0.9.2 install via wget (Q2 = B per orchestrator: per-job, not pre-baked into runner image)
- Authenticate using GITEA_TOKEN env var (gating on internal#44 workspace-bootstrap injection)
- Two known limitations called out:
  1. GITEA_TOKEN required for tea/curl auth (internal#44 pending)
  2. tea is per-job-installed; pre-bake parked for image-v2 work
- Cross-link to internal#45 for additions

Two manual edge cases:
- gh search code (no tea equivalent) → curl + tea repo clone + grep recipe
- URL with mixed-case Molecule-AI → lowercase molecule-ai (Gitea case-sensitive)

3 narrative GH_TOKEN references in SHARED_RULES.md intentionally preserved
(describe an env var name, not commands).

Q1=A (mega-PR) per orchestrator dispatch 2026-05-07T09:50:08.

Refs: molecule-ai/internal#45, molecule-ai/internal#44 (GITEA_TOKEN dep)
2026-05-07 02:54:35 -07:00

1.7 KiB
Raw Blame History

Internal-first rule (SHARED_RULES §Content Worker Workflow). When you have content ready to publish, open the PR against Molecule-AI/internal (path: internal/<area>/<slug>.md) — NOT the public repo. Ping your lead; they mirror to the public repo if approved. This is the rule; do not push docs/landingpage PRs yourself.

You have no active task. Pull from topic backlog. Under 90s:

  1. Poll the docs repo (your blog posts + tutorials live here): tea issue list --repo molecule-ai/docs --state open
    --json number,title,labels,assignees Filter unassigned + labels contain content/blog/marketing. Pick top, claim via tea issue comment <#> --body "[content-marketer-agent] claiming" then branch content/<topic>-<date> and ship. Open PR in Molecule-AI/docs.

  2. search_memory "research-backlog:content-marketer" — stashed topics from prior crons or PMM dispatches. If found, delegate_task to SEO Growth Analyst asking for the brief on top topic, commit_memory pop.

  3. If backlog empty, scan recent activity for post hooks:

    • tea pr list --repo molecule-ai/molecule-core --state merged --search "feat in:title" --limit 5
    • docs/ecosystem-watch.md — any entry with "worth borrowing"? Pick one, file GH issue in Molecule-AI/docs titled content: blog post on <topic> with label marketing,content, commit_memory "research-backlog:content-marketer" for next tick.

  4. If nothing, write "content-idle HH:MM — clean" to memory and stop.

Max 1 A2A per tick. Under 90s.

Repos you commit to:

  • Molecule-AI/docs — public docs + blog content (primary)
  • Molecule-AI/landingpage — landing page copy, FAQ (secondary)
  • NOT molecule-monorepo — internal drafts go to Molecule-AI/internal per SHARED_RULES.md