# Weekly content ideas

Every Monday, four or five content ideas, each tied to something that happened that week.

Requires web search, through Exa. Requires web fetch. Runs on a schedule.

## Install

```sh
npx @parcha/agentrun template install github:Parcha-ai/agentrun-templates/templates/content-ideas@242f29da8317fbe51d0cce4628bdb5ab61d7ccc9 --trust
```

Or open `<your AgentRun address>/#/templates/install?src=github%3AParcha-ai%2Fagentrun-templates%2Ftemplates%2Fcontent-ideas%40242f29da8317fbe51d0cce4628bdb5ab61d7ccc9`. Pinned to commit 242f29da8317fbe51d0cce4628bdb5ab61d7ccc9.

## What it does

Every Monday, four or five content ideas for your marketing team, each tied to something that happened this week in your audience's world (a new report, a rule change, a platform update, a search trend, a busy community thread) and linked to the page that makes it timely. Each idea says what to publish and in what format, numbers keep their source and period, and a week with nothing real is called quiet rather than filled with evergreen tips. Ideas it already gave you don't come back.

- Skill `content-ideas`: Write a weekly edition of content ideas for one company and audience. Find this week's verified hooks (news, reports, rule changes, platform changes, search trends, events, community threads), keep only those HOOKS.md accepts, turn each into one idea with a post to write and its format, drop what earlier editions already gave, and answer with the JSON. Use for the scheduled edition and for "what should we write about this week".
- Rules: `HOOKS.md`

## What starts it

- On a schedule: Mondays at 08:00 (UTC), unless you pick another time when you install it.
- By hand, any time: from the console, the API or the CLI.

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `company` | string, 2 to 160 characters | yes | Your company, with its website when it has one. Example: `Ledgerly (ledgerly.example)`. |
| `audience` | string, 2 to 300 characters | yes | Who you market to. Example: `Finance teams at mid-size US companies`. |
| `focus` | string, 0 to 300 characters | no | Blank: anything this audience cares about this week. |

### Setup, filled in once at install

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `company` | string | yes | Your company, with its website when it has one: "Ledgerly (ledgerly.example)" |
| `audience` | string | yes | Who you market to, in a few words: "finance teams at mid-size US companies" |
| `focus` | string | no | Optional: themes or channels to weigh most ("AP automation, LinkedIn") |
| `cron` | string, cron | no | When the edition is written, as a cron line (minute hour day-of-month month day-of-week): Monday 08:00 unless you set it. Default: `0 8 * * 1`. |
| `timezone` | string, timezone | no | The IANA time zone the cron line is read in (Europe/Madrid, America/New\_York): UTC unless you set it. Default: `UTC`. |

## What it needs

- Harness: pi, claude-agent, codex
- Model: balanced tier, medium effort
- Tools: read, web_search, web_fetch
- Computer: Wherever your AgentRun puts a new agent
- Keys: A model key
- Learning: on

## Sample output

Input:

```json
{
  "content": "Scheduled run, fired 2026-11-16T08:00:00Z (Monday). Write this week's content ideas with your content-ideas skill.\n\nThe sites below are not reachable from this run. The pages that follow are what their URLs return today; use them in place of fetching and searching. These sites are test data.\n\n--- https://ledgerly.example/ (fetched 2026-11-16) ---\n<h1>Ledgerly: accounts payable automation for mid-size finance teams</h1><p>Capture invoices, match them to POs and receipts, route approvals and pay vendors from one place.</p><p>Blog: \"How three-way matching works\" (2026-10-02), \"Approval workflows that auditors like\" (2026-10-20).</p>\n\n--- https://fpa-association.example/research/controller-pulse-2026 (fetched 2026-11-16) ---\n<h1>Controller Pulse 2026</h1><p>Published November 10, 2026. Survey of 840 controllers at US companies with $50M to $1B in revenue, fielded September 8 to 26, 2026.</p><p>61% say invoice exceptions (price or quantity mismatches) are the main cause of a late close. 44% still key some vendor invoices by hand. Median days to close: 8.</p>\n\n--- https://bpc.example/news/e-invoicing-framework-v2-final (fetched 2026-11-16) ---\n<h1>Business Payments Coalition publishes final US e-invoice exchange framework, version 2</h1><p>November 12, 2026. The framework sets a common format for invoices exchanged between US businesses' accounting systems. Version 2 adds credit notes and partial payments. It takes effect for participating networks on March 1, 2027.</p>\n\n--- https://trends.example/explore?q=invoice+fraud&geo=US&date=past-30-days (fetched 2026-11-16) ---\n<h2>Interest over time: \"invoice fraud\", United States, past 30 days</h2><p>Values are relative to the highest point on the chart (100).</p><p>Oct 17: 38 · Oct 24: 41 · Oct 31: 40 · Nov 7: 57 · Nov 13: 100 (peak)</p>\n\n--- https://reddit.example/r/Accounting/comments/8x2k1/ (fetched 2026-11-16) ---\n<h1>Our AP clerk paid a fake \"vendor bank change\" invoice for $48k. How do you verify bank changes?</h1><p>Posted November 11, 2026 · 1.2k points · 340 comments</p><p>Top comment: \"Call the vendor on a number you already have, never the one on the letter.\"</p>\n\n--- https://payflow.example/blog/cfo-survey (fetched 2026-11-16) ---\n<h1>80% of CFOs plan to replace their AP software in 2027</h1><p>November 13, 2026. A survey PayFlow commissioned of 200 CFOs found 80% plan to replace their AP tool next year. PayFlow is an AP automation vendor.</p>\n\n--- https://citynews.example/2026/11/14/warehouse-fire (fetched 2026-11-16) ---\n<h1>Three dead in warehouse fire at Ohio logistics firm</h1><p>November 14, 2026. Investigators are looking at the cause.</p>\n\n--- https://closeblog.example/10-tips-faster-close (fetched 2026-11-16) ---\n<h1>10 tips for a faster month-end close</h1><p>Published March 3, 2024.</p>",
  "company": "Ledgerly (ledgerly.example)",
  "audience": "Finance teams at mid-size US companies"
}
```

Output:

**Content ideas for Ledgerly** 2026-11-10 to 2026-11-16
US relative search interest in “invoice fraud” reached its chart peak on November 13—not evidence that fraud incidents increased.

1. **Invoice-fraud search interest peaked—not necessarily invoice fraud** (search_trend, Nov 13)
   The supplied trends page shows relative interest of 100 of 100 on November 13, versus 57 on November 7, for the United States over its past-30-days chart. These values measure relative search interest, not search counts or fraud incidence.
   Ledgerly can explain the limits of this attention signal without offering fraud-prevention advice or asserting an increase in losses.
   Post to write: A newsletter section, “Invoice fraud is trending: what the chart actually tells finance teams,” separating relative search interest from incident rates and losses. [source](https://trends.example/explore?q=invoice+fraud&geo=US&date=past-30-days)

2. **PayFlow’s 80% replacement claim needs its survey context** (report, Nov 13)
   PayFlow’s vendor survey, published November 13, says 80% of 200 surveyed CFOs plan to replace their AP software in 2027. The supplied page gives no fieldwork dates, geography, company sizes or recruitment methods.
   Ledgerly can explain why this is not a representative finding about mid-size US companies and identify the questions the headline leaves unanswered.
   Post to write: A LinkedIn post, “Before you repeat the 80% AP replacement headline,” identifying the vendor source, missing methodology and questions the figure leaves unanswered. [source](https://payflow.example/blog/cfo-survey)

3. **E-invoice framework v2 adds credit notes and partial payments** (regulation, Nov 12)
   The Business Payments Coalition’s November 12 announcement describes a common invoice-exchange format between US businesses’ accounting systems. Version 2 adds credit notes and partial payments and takes effect for participating networks on March 1, 2027.
   Explain the announced scope and its connection to AP workflows. Link readers to the standard body; do not present participation as a universal US legal requirement or imply Ledgerly compatibility.
   Post to write: A blog post, “E-invoice framework v2: what changed and who it affects,” explaining credit notes, partial payments and the participating-network effective date. [source](https://bpc.example/news/e-invoicing-framework-v2-final)

4. **Controller Pulse puts invoice exceptions at the late-close bottleneck** (report, Nov 10)
   Controller Pulse 2026 reports that 61% of 840 surveyed controllers at US companies with $50M–$1B revenue identify invoice exceptions—price or quantity mismatches—as the main cause of a late close. Published November 10; fielded September 8–26, 2026.
   Ledgerly can map exception ownership and resolution across AP workflows, moving beyond its existing introductory matching content without promising close-time improvements.
   Post to write: A carousel, “Where invoice exceptions stall the close,” tracing a price or quantity mismatch through detection, ownership, resolution and approval. [source](https://fpa-association.example/research/controller-pulse-2026)

_Plan ahead: E-invoice exchange framework v2 takes effect for participating networks on March 1, 2027. [Announcement](https://bpc.example/news/e-invoicing-framework-v2-final)._

Evidence note: These ideas rely on the supplied page snapshots. Independent corroboration was unavailable. No earlier-edition hooks were supplied for repeat checking.

## Tested

Passes 5 of 5 eval cases on pi, 3 of 5 on Claude Code and 5 of 5 on Codex. On the live web, 1 of 1 on pi, 1 of 1 on Claude Code and 1 of 1 on Codex.

6 eval cases: hooks-not-tips, injection-in-page, live-finance-week, no-repeats, quiet-week, search-failed.

## Source

- Package: https://github.com/Parcha-ai/agentrun-templates/tree/242f29da8317fbe51d0cce4628bdb5ab61d7ccc9/templates/content-ideas
- Publisher: Parcha-ai
- Author: Parcha Labs
- Version: 0.1.0
- License: Apache-2.0
- Category: Marketing
- Page: https://marketplace.agentrun.ai/templates/content-ideas/
