newspaper
- Repo stars 393
- License Apache-2.0
- Author updated Live
- Author repo gradient-bang
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @pipecat-ai · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Required · OpenAI
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Env read
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: newspaper
description: Generate Gradient News & Observer assets (banners, front pages, prompt experiments) by dispatchi…
category: ai
runtime: no special runtime
---
# newspaper output preview
## PART A: Task fit
- Use case: Generate Gradient News & Observer assets (banners, front pages, prompt experiments) by dispatching to the right newspaper script. Usage `/newspaper <asset-type> [args]` where asset-type is `banner`, `front-page`, or `prompt-experiment`..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Usage / All output goes under artifacts/ / Banner workflow” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Generate Gradient News & Observer assets (banners, front pages, prompt experiments) by dispatching to the right newspaper script. Usage `/newspaper <asset-type> [args]` where asset-type is `banner`, `front-page`, or `prompt-experiment`.”.
- **02** When the source has headings, the agent prioritizes “Usage / All output goes under artifacts/ / Banner workflow” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; may access external network resources; requires OpenAI API keys.
## Running Rules
- read files, write/modify files, read environment variables; may access external network resources; requires OpenAI API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/newspaper`, `/news-front-page`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, read environment variables.
Start with a small task and check whether the result follows “Usage / All output goes under artifacts/ / Banner workflow”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: newspaper
description: Generate Gradient News & Observer assets (banners, front pages, prompt experiments) by dispatchi…
category: ai
source: pipecat-ai/gradient-bang
---
# newspaper
## When to use
- Generate Gradient News & Observer assets (banners, front pages, prompt experiments) by dispatching to the right newspa…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Usage / All output goes under artifacts/ / Banner workflow” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; may access external network resources; requires OpenAI API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "newspaper" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Usage / All output goes under artifacts/ / Banner workflow
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, read environment variables | may access external network resources
guardrails -> requires OpenAI API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Newspaper Asset Generator
Single entry point for all Gradient News & Observer image assets. Routes to the underlying script based on the asset type.
Usage
/newspaper <asset-type> [args]
Asset types:
banner— single wide masthead-style banner (e.g. CALL TO ARMS recruiting header). Handled below.front-page— full ten-section newspaper front page from real game events. Hands off to/news-front-page— invoke that skill directly instead.prompt-experiment— sweep prompt variants for front-page rendering. Callsnews-front-page-prompt-experiment(see src/gradientbang/newspaper/scripts/prompt_experiment.py for flags).
If the user passes an unrecognized asset type, list the three options above and stop — do not guess.
All output goes under artifacts/
artifacts/ is gitignored. Both copy markdown and rendered PNGs live there. Subdirectories per asset type:
artifacts/banners/artifacts/gradient-news-observer-regions/(front-page composited)artifacts/gradient-news-observer-images/(front-page one-shot)
Banner workflow
A banner is a single wide image with one dramatic headline + short body + call-to-action. Used for recruiting drives, special-edition broadsides, channel headers, etc.
Step 1 — gather copy from the user
Required inputs:
- Headline (largest type — e.g.
CALL TO ARMS) - Subhead (one line — e.g.
Pilots Wanted to Test the Combat Rework) - Body (1–3 short sentences setting the stakes)
- Call to action (e.g.
Join the test → #gradient-bang)
Optional:
- Kicker (small caps line above the headline; defaults to
THE GRADIENT NEWS & OBSERVER · SPECIAL EDITION) - Slug (short filename stem, kebab-case; defaults to a slugified headline)
If the user's prompt only gives you a topic ("call to arms for combat rework"), draft kicker/headline/subhead/body/CTA yourself in the newspaper's voice and confirm with the user before rendering — image-edit calls take ~2 minutes and cost real money.
Step 2 — write the copy markdown
Write to artifacts/banners/<slug>.md using this exact structure (each line on its own line, blank lines between blocks). Every visible word in the file is rendered verbatim — no extra hidden formatting.
<KICKER>
<HEADLINE>
<Subhead>
<Body sentences.>
<Call to action>
Keep total visible word count under ~50 — banners get cramped fast. If body runs long, trim it.
Step 3 — render
set -a && source .env.bot && set +a
uv run news-banner --copy-file artifacts/banners/<slug>.md
- Sources
.env.botbecause that's whereOPENAI_API_KEYlives in this repo (the script also auto-loads it from.envif present). - Defaults to
2048x1024(clean 2:1 banner). For wider Discord-banner shapes, append--size 2880x1024. Both dims must be multiples of 16; max edge 3840; max ratio 3:1. - Defaults to the masthead reference. For a busier full-page-style aesthetic, append
--reference src/gradientbang/newspaper/assets/references/full-page-style-fri-sat-pt.png. - Render takes ~120–150s. Stream stdout — the script prints the final PNG path on success.
- Pass
--forceto overwrite an existing PNG with the same name.
Step 4 — show the result
Read the generated PNG so the image is visible in chat, then summarize with the artifact path. The user reviews and either accepts, edits the markdown and re-renders, or asks for a fresh take (image-edit isn't deterministic — same input can produce a different layout).
Front-page workflow
Don't replicate the front-page logic here. Tell the user:
Front pages are a different animal — they pull real game events into a structured digest, then render a 2160×3840 ten-story page. Use
/news-front-page [duration](e.g./news-front-page 24h).
If they explicitly want to re-render an existing markdown front page without regenerating the digest, they can call news-front-page-image --front-page-md <path> directly.
Prompt-experiment workflow
This is a power-user tool for sweeping prompt variants. Run with --help first to surface the flags, then construct the right command for the user's question:
uv run news-front-page-prompt-experiment --help
Rules
- Always confirm copy before spending an image-edit call. Each one costs and takes ~2 min. Cheap to iterate on markdown, expensive to iterate on images.
- Only edit
artifacts/for copy and outputs. Don't write undersrc/for one-off banners. - Don't invent new script entry points. If the user wants something the existing scripts don't support (e.g. a different aspect or new layout), discuss the trade-off before adding code.
- Don't commit anything. The user reviews artifacts and decides what to share.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review