SkillCDN 팩

A sourced topic brief for a card-news post

The categories an account covers go in, with who the post is for; a ranked list of this week's candidates comes out, the user picks one, and the pick becomes a topic brief: the angle as a published interpretation with its outlet and its sentence, every fact with the article sentence it rests on, numbers cross-checked, disagreements and unverified items listed, and the images that show the story on disk with captions, credits, pixel sizes, legibility and licence terms. The images come from where the articles point, in order: the articles' own photographs, the material the articles cite (a broadcaster's clip of the report, the footage or the post the story is about), the subject's own public pages, and an image search only for what those leave unshown; a photo that does not show the story is not an image of it, however well credited. The brief is what the build skill writes slides and the caption from, and it is the whole of what the slides may say and show: a reader who has met a confident, invented thesis once checks every sentence, so the brief makes that check possible before anything is designed. The first message says so: the facts, the angle, the images and the beats come from this skill; the script and the caption are written from them next, by the build skill.

How the user is involved

• Questions: the audience, once, in one message: the readers, always, as "Who are the readers: what do they know of the subject, and what of theirs does the story touch?", with what the request implies offered as the default so that one word continues ("non-technical readers who run a site through a hosting service, unless you say otherwise"), because a post written for a reader the user did not name reads as nobody's; in the same message the stance and the tone, with the request's implication as the default ("a report, neutral, unless you say otherwise"; "a side's case, aggressive" where the request names a side): "A neutral report, commentary, or a case for one side? Calm or aggressive?"; and how the images' terms are to be handled: "Every image's terms at each stop, only the terms that forbid the use, or listed once at the delivery and left to you?"; and the half the request leaves open of the market and the language: "Which country or market?" when "domestic" names no country and neither the post's language nor the spec's account points to one market, "In which language will the post be?" when neither the request nor the market's one language says. The categories, when neither the request nor a format spec gives them. Nothing else is asked.
• Checkpoints: the candidate list, where the user picks, with one card recommended (a stop that is not skipped: the pick is theirs); the brief, in plain words, before it is delivered. Picking a story also accepts that its images are collected into the brief folder (the articles' photos, frames of a clip they cite, the subject's public images, an image search where those leave a beat unshown), and the brief checkpoint lists each file with where it came from, what it shows, its size and its legibility. A story handed over in the request is the pick, and the list is not shown.
• Go-ahead: when the user says to go ahead alone after the pick, the brief checkpoint is skipped; the pick itself is never made by the skill.
• Changes mid-run: "domestic, not global" re-ranks the candidates; a fact the user doubts is re-read in its article, and the chat points to its id while the quoted sentence lives in the brief.

Requirements

Check the first three before the first message, and the optional browser after the pick, when a cited clip makes frames wanted. Without search, stop and say what to add; without a page reader, facts cannot be sourced and the run stops at the candidate list. No paywall is bypassed and no account is signed in to: an article that cannot be read in full is not a source. What the card-news skills share is in the repository's document set docs/card-news/; topic-brief.md, the fields of what this skill writes and how the build reads them, is included and arrives with this skill wherever SkillCDN serves it, and format-spec.md is read through the repository connection when a spec exists. reading-pages.md from the repository's document set docs/browser/ is included too; that set's walls.md is read when a source's site fails from its first page while other sites load, and video-frames.md and headless.md phase 3 reads when a clip is a source. A copy of this directory and the area's plugin lack the included pages, and a copy, the plugin and a mount of one area or one skill cannot read the linked ones: say so, fetch them from docs/card-news/ and docs/browser/ of the repository this skill comes from (for this pack, github.com/skillcdn/skills), and otherwise write the brief by the example in topic-brief.example.json, which is the shape, and read a spec's fields as its file is. How the tools behaved in runs of this skill is in tool-notes.md; read it before phase 1.

The area's rules that evidence stays apart from inference and that assumptions are written down take this form for a news post: a fact is an article's sentence, the angle is an outlet's published reading and never the agent's, what no article confirmed is listed as unverified, and the images are the outlets', agencies', broadcasters' and subjects' material, used as the account itself uses such material, with their credits. The skill records each image's source, credit and terms and leaves the use to the user, who is told so at every delivery; a user who prefers their own images supplies them, and the entries then carry the user's files.

Inputs