Install
$ agentstack add skill-jiahuiqu17-paper-signal-paper-signal-series ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Paper Signal Series
Turn content into a sequence with one editorial promise and several visually distinct images. Shared material creates continuity; each card's subject controls its composition.
Load the shared system
Read these companion files from ../paper-signal/:
references/core-workflow.mdreferences/subject-routing.mdreferences/visual-language.mdreferences/content-architecture.mdreferences/presets.mdreferences/prompt-compiler.mdreferences/quality-contract.md
Read references/evidence-ledger.md for factual claims and references/human-voice.md for personal-sharing or recommendation copy.
Workflow
1. Resolve the post promise
Write one sentence describing what the viewer will feel, understand, or decide after the final swipe. Split unrelated outcomes into separate posts.
Extract platform, audience, source material, language, image count, visible text, supplied photos, exact facts, caption need, public-source-label policy, and output destination.
2. Choose the sequence strategy
Select one:
story-led— atmosphere or experience opens the sequence; reveal context gradually.value-led— conclusion first; follow with useful evidence, tradeoffs, and fit.visual-led— hero image first; alternate context, detail, object, person, and pause.
Recommend one strategy and count. Default to 4-6 images for ordinary social posts and three substantial items when each needs facts, tradeoffs, and fit.
3. Build the content architecture
Create:
analysis.md— promise, audience tension, source/evidence map, scope, and visual opportunitiesoutline.md— one job, takeaway, exact on-image text, subject route, composition mode, caption handoff, and swipe reason per imagecaption.md— natural publishable copy when requestedevidence.json— only when facts, reviews, rankings, numbers, or source documents are involved
Keep one dominant idea per image. Move nuance to the caption.
4. Route every image independently
Assign each image a subject route and composition mode. A landscape card may use panorama-strip; a portrait may use portrait-archive; an object may use specimen-plate; evidence may use dual-frame or airy-fragment.
Lock across the series:
- paper family and aging level
- one lead reproduction process
- type pairing
- anchor hue or tightly controlled hue progression
- texture intensity and safe-zone behaviour
Vary image scale, crop, composition, subject route, color form, and type behaviour. Do not clone the cover layout.
5. Save every prompt
Write every four-paragraph prompt to prompts/NN-{role}-{slug}.md before any generation call. Verify the complete prompt group exists.
Use exact strings only. Never invent quotes, reviews, dates, coordinates, archive codes, pseudo-language, or first-person experience.
6. Confirm once
Show strategy, count, card roles, subject/composition sequence, preset, process, hue, caption voice, source-label policy, and output directory. Skip only when the user explicitly asks for direct/default generation.
7. Generate the series
- Render image 1 without a previous-card reference.
- Inspect and accept it as the material anchor.
- Render images 2+ as distinct calls, using image 1 as a style/series reference when supported.
- Keep direct batches to four or fewer calls.
- Retry only failed images, once each, with one targeted correction.
- Copy selected outputs into
outputs/with stable ordered filenames.
Use the runtime-native bitmap generator. In Codex, use built-in imagegen. Never substitute code-rendered posters or patch generated text with overlays.
8. Audit and deliver
Run the shared quality contract and project validator. Inspect every image at full size and thumbnail size, then inspect the whole sequence as a strip.
Deliver images inline, absolute paths, final caption, selected strategy, material system, validation result, and any honest evidence or rendering caveats.
Sequence anti-patterns
- every card uses a tiny centered fragment regardless of subject
- every card is a different visual style
- cover reference forces identical layout later
- atmosphere is manufactured with random pseudo-text
- information cards become dashboard grids on vintage paper
- landscapes are decorative thumbnails and portraits lose identity
- caption repeats the bitmap instead of adding nuance
- generic ending demands likes/follows without helping the reader
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jiahuiqu17
- Source: jiahuiqu17/paper-signal
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.