[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESQ4RTPJC039PEDXDG3B7G":3,"skill-same:01M7ESQ4RTPJC039PEDXDG3B7G":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7ESQ4RTPJC039PEDXDG3B7G","shortform-strategy",null,"Use when the unit of work is a TikTok\u002FReels account, not one clip: positioning, sustainable cadence and format mix, ride-or-skip on a trend or sound, recurring series, diagnosing a flat account, and the dated learning loop. NOT the single script or hook variants (that is `video-shorts`), NOT the idea backlog (that is `shortform-ideation`).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fshortform-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: shortform-strategy\ndescription: \"Use when the unit of work is a TikTok\u002FReels account, not one clip: positioning, sustainable cadence and format mix, ride-or-skip on a trend or sound, recurring series, diagnosing a flat account, and the dated learning loop. NOT the single script or hook variants (that is `video-shorts`), NOT the idea backlog (that is `shortform-ideation`).\"\ntags: [short-form-video, tiktok, instagram-reels, account-growth, positioning, posting-cadence, trends, series, algorithm-2026]\nrecommends: [video-shorts, shortform-ideation, shortform-packaging, shortform-editing, social-publisher, content-engine, brand-voice, analytics]\norigin: risco\n---\n\n# Shortform Strategy — The Account Operating System\n\n*You own the account, not the clip.* You decide who it is for, how often it posts, what mix of formats, which trends it rides, which series it runs — and you keep a written record of what actually moved the numbers so the next call is grounded, not vibes. You produce a **strategy doc**, a **posting plan**, and a **decision log**. You never write the script, the cover, the caption, or the cut.\n\nHand off downstream the moment the deliverable becomes *one video*:\n- The 15–60s script and hook variants → `..\u002Fvideo-shorts\u002FSKILL.md`.\n- The topic\u002Fangle backlog feeding the account → `..\u002Fshortform-ideation\u002FSKILL.md`.\n- The cover frame \u002F on-screen title \u002F first-frame packaging → `..\u002Fshortform-packaging\u002FSKILL.md`.\n- The cut, caption burn-in, sound sync → `..\u002Fshortform-editing\u002FSKILL.md`.\n- Cross-platform calendar\u002Fscheduler across X\u002FLinkedIn\u002FThreads → `..\u002Fsocial-publisher\u002FSKILL.md`.\n- The top-down editorial system across all content types → `..\u002Fcontent-engine\u002FSKILL.md`.\n- The durable tone the account speaks in → `..\u002Fbrand-voice\u002FSKILL.md`.\n\n**Boundary test:** if it is one asset, route it. If it is *what the whole account does, on what rhythm, and the record of what worked* — it is yours.\n\n## Step 0 — Read the ledger before you decide anything\n\nStrategy without memory is just opinion. Before any call, read what the account already learned:\n\n- `02-DOCS\u002Fwiki\u002Fshortform\u002F` — the compiled strategy, positioning, and dated decisions.\n- `02-DOCS\u002Fraw\u002Fshortform\u002F` — the per-post metrics ledger (completion %, sends, saves, follows).\n\n*Why: the account is a feedback loop. If you cannot point to the prior decision and the metric that backs it, you are guessing — and you will re-make a mistake the ledger already recorded.* If the directories are empty, this is a new account: say so explicitly and create the baseline in Step 0's write-back, then proceed to Positioning.\n\nThe numbers below age fast. The dated, sourced cheat-sheet lives in `references\u002Fplatform-signals-2026.md` — cite it, do not re-derive it.\n\n## Positioning — the one promise and the lane\n\nAn account grows when a stranger can finish your video and instantly know *what they get if they follow*. Vague accounts do not grow; specific lanes do — \"productivity for remote workers\", \"true crime in 5 minutes\" — because the algorithm rewards retention and a tight lane is what holds a cohort to the end (almcorp.com short-form mastery 2026; virvid.ai faceless 2026 — accessed 2026-06-02).\n\nWrite the positioning as one sentence: **`\u003Cfor whom>` gets `\u003Cone promise>` in `\u003Cformat\u002Flane>`.** If you cannot, the account has no lane yet — narrow before you post.\n\nFaceless is fine. Retention, not a face, is what the algorithm scores. A faceless account is viable *if the retention holds*; if it does not, the problem is the lane or the hook, never the missing face.\n\n| Signal | Diagnosis | Move |\n|---|---|---|\n| Clear one-promise sentence + completion holding | Lane is working | Proceed to cadence |\n| Sentence is fuzzy \u002F lists 3+ niches | No lane — this is the growth blocker | Narrow to ONE promise, re-test 2 weeks |\n| Clear lane but completion \u003C niche bar | Lane fine, execution weak | Fix hook\u002Flength (hand to `..\u002Fvideo-shorts\u002FSKILL.md`), not the lane |\n| Faceless, retention proven | Viable | Keep faceless; do not chase a face |\n\n## Cadence and mix — consistency beats velocity\n\nPick the rhythm the account can *sustain*. Consistency now outperforms sporadic viral hits, and posting past the ceiling dilutes quality and burns the operator out (automateed.com; truescho.com; newzenler.com — accessed 2026-06-02).\n\n| Account \u002F platform | Cadence | Why |\n|---|---|---|\n| TikTok | 3–5 quality posts\u002Fweek | Consistency sweet spot; daily-but-thin loses to fewer-but-sharper |\n| Instagram Reels | 4–7 Reels\u002Fweek | Reach-vs-engagement optimum |\n| Instagram full mix (weekly) | 3–4 Reels + 2–3 carousels + 1–2 statics | Reels drive growth; carousels drive depth |\n| Any platform | Hard ceiling ~10\u002Fweek | Past this: diminishing returns + burnout + quality dilution |\n\n**Format mix rule (Instagram):** carousels now average ~10% engagement vs ~6% for regular Reels and get a \"second chance\" surge of 2–3× impressions — but **for small accounts Reels remain the biggest visibility driver** (thesecondbrain.io; reelbase.io; usevisuals.com — accessed 2026-06-02). So: lean Reels for *growth*, carousels for *sales\u002Fcommunity*. Do not pile into carousels on a small account chasing the engagement headline — you will trade reach you need for engagement you do not yet.\n\nBad → Good:\n- Bad: \"We'll post twice a day to grow faster.\"\n- Good: \"4 Reels\u002Fweek we can actually make well, same two days each week, for 4 weeks; we raise volume only if completion holds.\"\n\n## Hook-first at the account level\n\nMake the account's KPI **first-3s retention and completion %**, not views or likes. The first 3 seconds decide a Reel, and watch-time\u002Fcompletion is the strongest retention signal — a fully-watched 15s beats a 60s most people abandon (truefuturemedia.com; buffer.com — accessed 2026-06-02). On TikTok the 2026 bar rose: ~70%+ completion to go viral (up from ~50% in 2024), and an 85% completion threshold trips a ~4× distribution multiplier (socialboostdigital.com; socialync.io — accessed 2026-06-02).\n\nSet length bands as account policy, then let depth get scripted downstream:\n\n| Goal | Length band | Why |\n|---|---|---|\n| New-audience reach + completion | 7–30s | Easiest to fully watch; clears the completion bar |\n| Depth with existing followers | 30–90s | Room to teach; full 7–90s is the highest-viral band |\n\nYou set the band and the KPI. The actual hook and per-second pacing is `..\u002Fvideo-shorts\u002FSKILL.md`'s job — point to it, do not write it here.\n\n## Trends and sounds — the ride-or-skip call\n\nIn 2026 a trending sound is a **niche\u002Fcategory signal, not a raw boost**. Using a sound trending *within your niche* nudges TikTok to drop your test cohort into that niche (which raises completion); the 2022–2024 direct distribution boost is gone. Adopt within ~24h of it trending or skip it (sproutsocial.com; opus.pro — accessed 2026-06-02).\n\nRun the call as a gate — all three must be yes to ride:\n\n```text\n1. Is the sound\u002Ftrend trending WITHIN our niche (not just globally)?   no -> SKIP\n2. Is it \u003C ~24h old (still on the rising edge)?                        no -> SKIP\n3. Does the format fit our positioning without contorting it?         no -> SKIP\nall yes -> RIDE: ship within 24h, treat the first ~30 minutes as the test\n```\n\nWhy the 30-minute window matters: \"view velocity\" — engagement inside roughly the first 30 minutes of distribution — is a dominant early signal in 2026 (socialboostdigital.com; socialync.io — accessed 2026-06-02). A trend you publish late, off-niche, or twisted to fit gives you all the production cost and none of the cohort lift. When in doubt, **skip** — a missed trend costs nothing; a forced one costs a slot and muddies your lane.\n\n## Series — the compounding move\n\nMulti-part series drive roughly **2.8× higher return viewers** because a recurring format builds the habit the algorithm rewards (socialboostdigital.com; socialync.io — accessed 2026-06-02). A series is the cheapest durable lift you can design.\n\nDesign it as a *contract with the viewer*:\n- **Name + number it** — \"Tiny Systems #07\" — so a returning viewer recognizes it in the first frame.\n- **Fix a cadence** — same slot, same rhythm (e.g. every Tuesday). A series with no schedule is just a hashtag.\n- **Pilot before committing.** Use **Trial Reels** (public IG accounts, 1,000+ followers, available since July 2025) to publish the pilot to non-followers first and read the signal before showing your existing audience — a built-in A\u002FB surface for a format bet (later.com; socialpilot.co — accessed 2026-06-02).\n\nThe hand-off: you define the series *concept, cadence, and numbering*. The episodes get ideated (`..\u002Fshortform-ideation\u002FSKILL.md`), scripted (`..\u002Fvideo-shorts\u002FSKILL.md`), and packaged (`..\u002Fshortform-packaging\u002FSKILL.md`) elsewhere.\n\n## The learning loop — log, review, write back\n\nEvery decision must end up in the ledger so next month's call is grounded.\n\n**Log per post** (not just likes): date, platform, format, hook, length, sound, **completion %**, **sends**, **saves**, follows, notes. DM sends are the top distribution signal for Reels in 2026 — share-via-DM carries the most weight for unconnected reach, and shares\u002Fsaves outrank likes (later.com; truefuturemedia.com; mirra.my — accessed 2026-06-02). If you only log likes and views, you are blind to the signal that actually moves reach.\n\n**Monthly review ritual:** read the ledger, find the top-3 and bottom-3 by completion and by sends, name the pattern, make one positioning\u002Fcadence\u002Fseries change, and record it as a dated decision. The full per-post schema, review checklist, and decision-record template live in `references\u002Flearning-loop-template.md` — use it verbatim so the ledger stays machine-readable.\n\n### Decision record format\n\n`02-DOCS\u002Fwiki\u002Fshortform\u002Fdecisions.md` is an OKF append-log: write the frontmatter\nheader once (a non-empty `type` is the only OKF hard requirement; `title`\u002F`tags`\u002F`timestamp`\nare the recommended surface), then **prepend each new dated block newest-first** so the\nlatest call is on top. Use ISO 8601 dates; never edit a past block. Bump the header\n`timestamp` on each append. Header + one block:\n\n```markdown\n---\ntype: shortform-decision-log\ntitle: Shortform strategy decisions\ntags: [shortform, strategy, decisions]\ntimestamp: 2026-06-02T10:00:00Z\n---\n# Shortform strategy decisions\n\n## 2026-06-02 — Drop daily posting to 4 Reels\u002Fweek\n**Decision:** Cut from ~7 thin posts\u002Fweek to 4 strong Reels\u002Fweek, fixed Tue\u002FFri.\n**Rationale:** Reach fell as volume rose; consistency > velocity past the ceiling.\n**Rests on:** completion avg 31% (ledger), cadence-ceiling signal (platform-signals-2026).\n**Revisit on:** 2026-07-02 — keep if completion clears 40% and sends\u002Fpost rise.\n```\n\n*Why dated + rests-on + revisit: a decision you cannot trace to a metric and a date is folklore. The revisit line turns it into an experiment with an end.*\n\n## Anti-patterns\n\n| Anti-pattern | Why it fails | Do instead |\n|---|---|---|\n| Riding a trend after it peaked \u002F off-niche | Sound is a niche signal now, not a boost; late + off-niche = cost, no lift | Run the 3-gate ride-or-skip; ship within 24h or skip |\n| Cross-posting identical creative everywhere | An Originality Score suppresses recycled\u002Freposted content | Re-cut natively per platform; treat each as original |\n| Posting 10+\u002Fweek to \"grow faster\" | Diminishing returns + burnout + quality dilution | Hold 3–5 (TikTok) \u002F 4–7 (Reels); raise only if completion holds |\n| Optimizing likes\u002Fviews | Sends\u002Fsaves\u002Fcompletion are what move reach; likes are vanity | KPI = completion % + sends\u002Fsaves; log them per post |\n| No clear lane (\"a bit of everything\") | Algorithm rewards retention; a fuzzy lane never holds a cohort | One-promise sentence first; narrow before posting |\n| Hashtag-spamming for discovery | Discovery shifted to keywords; hashtags no longer support follows | Keywords in caption\u002Fprofile\u002Fon-screen text; drop the hashtag wall |\n| \"Series\" with no fixed schedule | No habit forms; it is just a tag, no return-viewer lift | Name + number + fixed slot; pilot via Trial Reels |\n| Deciding from vibes, not the ledger | Re-makes recorded mistakes; nothing compounds | Read `02-DOCS\u002F...` first; every call gets a dated decision record |\n\n## Persist it\n\nWrite the account's brain back so it compounds (mirrors the harness Karpathy-wiki convention). The `shortform\u002F` wiki tree is an **OKF v0.1 bundle** shared with the `..\u002Ftiktok-api\u002FSKILL.md` and `..\u002Fshortform-packaging\u002FSKILL.md` siblings: every `.md` written here carries YAML frontmatter with a non-empty `type`, cross-references are standard markdown links (never `[[wikilinks]]`), and `decisions.md` follows the OKF newest-first append-log rule.\n\n- `02-DOCS\u002Fwiki\u002Fshortform\u002Fstrategy.md` — positioning, cadence\u002Fmix, KPI, length bands, current series. Same frontmatter shape as above with `type: shortform-strategy`, then the H1 (`# Shortform account strategy`) and the sections the linter checks.\n- `02-DOCS\u002Fwiki\u002Fshortform\u002Fdecisions.md` — the dated decision log, OKF append-log (`type: shortform-decision-log`, newest block on top; format above).\n- `02-DOCS\u002Fraw\u002Fshortform\u002Fmetrics.csv` — the per-post ledger (schema in `references\u002Flearning-loop-template.md`). This is `raw\u002F`, not `wiki\u002F` — a CSV, no frontmatter.\n\nVerify a produced strategy doc with `scripts\u002Fverify.sh 02-DOCS\u002Fwiki\u002Fshortform\u002Fstrategy.md` — a read-only structural lint (positioning, cadence, completion KPI, ride-or-skip rule, ≥1 dated decision, sends\u002Fsaves logged). The lint reads body content, so the added frontmatter does not affect it.\n","# Shortform Strategy — The Account Operating System\n\n*You own the account, not the clip.* You decide who it is for, how often it posts, what mix of formats, which trends it rides, which series it runs — and you keep a written record of what actually moved the numbers so the next call is grounded, not vibes. You produce a **strategy doc**, a **posting plan**, and a **decision log**. You never write the script, the cover, the caption, or the cut.\n\nHand off downstream the moment the deliverable becomes *one video*:\n- The 15–60s script and hook variants → `..\u002Fvideo-shorts\u002FSKILL.md`.\n- The topic\u002Fangle backlog feeding the account → `..\u002Fshortform-ideation\u002FSKILL.md`.\n- The cover frame \u002F on-screen title \u002F first-frame packaging → `..\u002Fshortform-packaging\u002FSKILL.md`.\n- The cut, caption burn-in, sound sync → `..\u002Fshortform-editing\u002FSKILL.md`.\n- Cross-platform calendar\u002Fscheduler across X\u002FLinkedIn\u002FThreads → `..\u002Fsocial-publisher\u002FSKILL.md`.\n- The top-down editorial system across all content types → `..\u002Fcontent-engine\u002FSKILL.md`.\n- The durable tone the account speaks in → `..\u002Fbrand-voice\u002FSKILL.md`.\n\n**Boundary test:** if it is one asset, route it. If it is *what the whole account does, on what rhythm, and the record of what worked* — it is yours.\n\n## Step 0 — Read the ledger before you decide anything\n\nStrategy without memory is just opinion. Before any call, read what the account already learned:\n\n- `02-DOCS\u002Fwiki\u002Fshortform\u002F` — the compiled strategy, positioning, and dated decisions.\n- `02-DOCS\u002Fraw\u002Fshortform\u002F` — the per-post metrics ledger (completion %, sends, saves, follows).\n\n*Why: the account is a feedback loop. If you cannot point to the prior decision and the metric that backs it, you are guessing — and you will re-make a mistake the ledger already recorded.* If the directories are empty, this is a new account: say so explicitly and create the baseline in Step 0's write-back, then proceed to Positioning.\n\nThe numbers below age fast. The dated, sourced cheat-sheet lives in `references\u002Fplatform-signals-2026.md` — cite it, do not re-derive it.\n\n## Positioning — the one promise and the lane\n\nAn account grows when a stranger can finish your video and instantly know *what they get if they follow*. Vague accounts do not grow; specific lanes do — \"productivity for remote workers\", \"true crime in 5 minutes\" — because the algorithm rewards retention and a tight lane is what holds a cohort to the end (almcorp.com short-form mastery 2026; virvid.ai faceless 2026 — accessed 2026-06-02).\n\nWrite the positioning as one sentence: **`\u003Cfor whom>` gets `\u003Cone promise>` in `\u003Cformat\u002Flane>`.** If you cannot, the account has no lane yet — narrow before you post.\n\nFaceless is fine. Retention, not a face, is what the algorithm scores. A faceless account is viable *if the retention holds*; if it does not, the problem is the lane or the hook, never the missing face.\n\n| Signal | Diagnosis | Move |\n|---|---|---|\n| Clear one-promise sentence + completion holding | Lane is working | Proceed to cadence |\n| Sentence is fuzzy \u002F lists 3+ niches | No lane — this is the growth blocker | Narrow to ONE promise, re-test 2 weeks |\n| Clear lane but completion \u003C niche bar | Lane fine, execution weak | Fix hook\u002Flength (hand to `..\u002Fvideo-shorts\u002FSKILL.md`), not the lane |\n| Faceless, retention proven | Viable | Keep faceless; do not chase a face |\n\n## Cadence and mix — consistency beats velocity\n\nPick the rhythm the account can *sustain*. Consistency now outperforms sporadic viral hits, and posting past the ceiling dilutes quality and burns the operator out (automateed.com; truescho.com; newzenler.com — accessed 2026-06-02).\n\n| Account \u002F platform | Cadence | Why |\n|---|---|---|\n| TikTok | 3–5 quality posts\u002Fweek | Consistency sweet spot; daily-but-thin loses to fewer-but-sharper |\n| Instagram Reels | 4–7 Reels\u002Fweek | Reach-vs-engagement optimum |\n| Instagram full mix (weekly) | 3–4 Reels + 2–3 carousels + 1–2 statics | Reels drive growth; carousels drive depth |\n| Any platform | Hard ceiling ~10\u002Fweek | Past this: diminishing returns + burnout + quality dilution |\n\n**Format mix rule (Instagram):** carousels now average ~10% engagement vs ~6% for regular Reels and get a \"second chance\" surge of 2–3× impressions — but **for small accounts Reels remain the biggest visibility driver** (thesecondbrain.io; reelbase.io; usevisuals.com — accessed 2026-06-02). So: lean Reels for *growth*, carousels for *sales\u002Fcommunity*. Do not pile into carousels on a small account chasing the engagement headline — you will trade reach you need for engagement you do not yet.\n\nBad → Good:\n- Bad: \"We'll post twice a day to grow faster.\"\n- Good: \"4 Reels\u002Fweek we can actually make well, same two days each week, for 4 weeks; we raise volume only if completion holds.\"\n\n## Hook-first at the account level\n\nMake the account's KPI **first-3s retention and completion %**, not views or likes. The first 3 seconds decide a Reel, and watch-time\u002Fcompletion is the strongest retention signal — a fully-watched 15s beats a 60s most people abandon (truefuturemedia.com; buffer.com — accessed 2026-06-02). On TikTok the 2026 bar rose: ~70%+ completion to go viral (up from ~50% in 2024), and an 85% completion threshold trips a ~4× distribution multiplier (socialboostdigital.com; socialync.io — accessed 2026-06-02).\n\nSet length bands as account policy, then let depth get scripted downstream:\n\n| Goal | Length band | Why |\n|---|---|---|\n| New-audience reach + completion | 7–30s | Easiest to fully watch; clears the completion bar |\n| Depth with existing followers | 30–90s | Room to teach; full 7–90s is the highest-viral band |\n\nYou set the band and the KPI. The actual hook and per-second pacing is `..\u002Fvideo-shorts\u002FSKILL.md`'s job — point to it, do not write it here.\n\n## Trends and sounds — the ride-or-skip call\n\nIn 2026 a trending sound is a **niche\u002Fcategory signal, not a raw boost**. Using a sound trending *within your niche* nudges TikTok to drop your test cohort into that niche (which raises completion); the 2022–2024 direct distribution boost is gone. Adopt within ~24h of it trending or skip it (sproutsocial.com; opus.pro — accessed 2026-06-02).\n\nRun the call as a gate — all three must be yes to ride:\n\n```text\n1. Is the sound\u002Ftrend trending WITHIN our niche (not just globally)?   no -> SKIP\n2. Is it \u003C ~24h old (still on the rising edge)?                        no -> SKIP\n3. Does the format fit our positioning without contorting it?         no -> SKIP\nall yes -> RIDE: ship within 24h, treat the first ~30 minutes as the test\n```\n\nWhy the 30-minute window matters: \"view velocity\" — engagement inside roughly the first 30 minutes of distribution — is a dominant early signal in 2026 (socialboostdigital.com; socialync.io — accessed 2026-06-02). A trend you publish late, off-niche, or twisted to fit gives you all the production cost and none of the cohort lift. When in doubt, **skip** — a missed trend costs nothing; a forced one costs a slot and muddies your lane.\n\n## Series — the compounding move\n\nMulti-part series drive roughly **2.8× higher return viewers** because a recurring format builds the habit the algorithm rewards (socialboostdigital.com; socialync.io — accessed 2026-06-02). A series is the cheapest durable lift you can design.\n\nDesign it as a *contract with the viewer*:\n- **Name + number it** — \"Tiny Systems #07\" — so a returning viewer recognizes it in the first frame.\n- **Fix a cadence** — same slot, same rhythm (e.g. every Tuesday). A series with no schedule is just a hashtag.\n- **Pilot before committing.** Use **Trial Reels** (public IG accounts, 1,000+ followers, available since July 2025) to publish the pilot to non-followers first and read the signal before showing your existing audience — a built-in A\u002FB surface for a format bet (later.com; socialpilot.co — accessed 2026-06-02).\n\nThe hand-off: you define the series *concept, cadence, and numbering*. The episodes get ideated (`..\u002Fshortform-ideation\u002FSKILL.md`), scripted (`..\u002Fvideo-shorts\u002FSKILL.md`), and packaged (`..\u002Fshortform-packaging\u002FSKILL.md`) elsewhere.\n\n## The learning loop — log, review, write back\n\nEvery decision must end up in the ledger so next month's call is grounded.\n\n**Log per post** (not just likes): date, platform, format, hook, length, sound, **completion %**, **sends**, **saves**, follows, notes. DM sends are the top distribution signal for Reels in 2026 — share-via-DM carries the most weight for unconnected reach, and shares\u002Fsaves outrank likes (later.com; truefuturemedia.com; mirra.my — accessed 2026-06-02). If you only log likes and views, you are blind to the signal that actually moves reach.\n\n**Monthly review ritual:** read the ledger, find the top-3 and bottom-3 by completion and by sends, name the pattern, make one positioning\u002Fcadence\u002Fseries change, and record it as a dated decision. The full per-post schema, review checklist, and decision-record template live in `references\u002Flearning-loop-template.md` — use it verbatim so the ledger stays machine-readable.\n\n### Decision record format\n\n`02-DOCS\u002Fwiki\u002Fshortform\u002Fdecisions.md` is an OKF append-log: write the frontmatter\nheader once (a non-empty `type` is the only OKF hard requirement; `title`\u002F`tags`\u002F`timestamp`\nare the recommended surface), then **prepend each new dated block newest-first** so the\nlatest call is on top. Use ISO 8601 dates; never edit a past block. Bump the header\n`timestamp` on each append. Header + one block:\n\n```markdown\n---\ntype: shortform-decision-log\ntitle: Shortform strategy decisions\ntags: [shortform, strategy, decisions]\ntimestamp: 2026-06-02T10:00:00Z\n---\n# Shortform strategy decisions\n\n## 2026-06-02 — Drop daily posting to 4 Reels\u002Fweek\n**Decision:** Cut from ~7 thin posts\u002Fweek to 4 strong Reels\u002Fweek, fixed Tue\u002FFri.\n**Rationale:** Reach fell as volume rose; consistency > velocity past the ceiling.\n**Rests on:** completion avg 31% (ledger), cadence-ceiling signal (platform-signals-2026).\n**Revisit on:** 2026-07-02 — keep if completion clears 40% and sends\u002Fpost rise.\n```\n\n*Why dated + rests-on + revisit: a decision you cannot trace to a metric and a date is folklore. The revisit line turns it into an experiment with an end.*\n\n## Anti-patterns\n\n| Anti-pattern | Why it fails | Do instead |\n|---|---|---|\n| Riding a trend after it peaked \u002F off-niche | Sound is a niche signal now, not a boost; late + off-niche = cost, no lift | Run the 3-gate ride-or-skip; ship within 24h or skip |\n| Cross-posting identical creative everywhere | An Originality Score suppresses recycled\u002Freposted content | Re-cut natively per platform; treat each as original |\n| Posting 10+\u002Fweek to \"grow faster\" | Diminishing returns + burnout + quality dilution | Hold 3–5 (TikTok) \u002F 4–7 (Reels); raise only if completion holds |\n| Optimizing likes\u002Fviews | Sends\u002Fsaves\u002Fcompletion are what move reach; likes are vanity | KPI = completion % + sends\u002Fsaves; log them per post |\n| No clear lane (\"a bit of everything\") | Algorithm rewards retention; a fuzzy lane never holds a cohort | One-promise sentence first; narrow before posting |\n| Hashtag-spamming for discovery | Discovery shifted to keywords; hashtags no longer support follows | Keywords in caption\u002Fprofile\u002Fon-screen text; drop the hashtag wall |\n| \"Series\" with no fixed schedule | No habit forms; it is just a tag, no return-viewer lift | Name + number + fixed slot; pilot via Trial Reels |\n| Deciding from vibes, not the ledger | Re-makes recorded mistakes; nothing compounds | Read `02-DOCS\u002F...` first; every call gets a dated decision record |\n\n## Persist it\n\nWrite the account's brain back so it compounds (mirrors the harness Karpathy-wiki convention). The `shortform\u002F` wiki tree is an **OKF v0.1 bundle** shared with the `..\u002Ftiktok-api\u002FSKILL.md` and `..\u002Fshortform-packaging\u002FSKILL.md` siblings: every `.md` written here carries YAML frontmatter with a non-empty `type`, cross-references are standard markdown links (never `[[wikilinks]]`), and `decisions.md` follows the OKF newest-first append-log rule.\n\n- `02-DOCS\u002Fwiki\u002Fshortform\u002Fstrategy.md` — positioning, cadence\u002Fmix, KPI, length bands, current series. Same frontmatter shape as above with `type: shortform-strategy`, then the H1 (`# Shortform account strategy`) and the sections the linter checks.\n- `02-DOCS\u002Fwiki\u002Fshortform\u002Fdecisions.md` — the dated decision log, OKF append-log (`type: shortform-decision-log`, newest block on top; format above).\n- `02-DOCS\u002Fraw\u002Fshortform\u002Fmetrics.csv` — the per-post ledger (schema in `references\u002Flearning-loop-template.md`). This is `raw\u002F`, not `wiki\u002F` — a CSV, no frontmatter.\n\nVerify a produced strategy doc with `scripts\u002Fverify.sh 02-DOCS\u002Fwiki\u002Fshortform\u002Fstrategy.md` — a read-only structural lint (positioning, cadence, completion KPI, ride-or-skip rule, ≥1 dated decision, sends\u002Fsaves logged). The lint reads body content, so the added frontmatter does not affect it.\n",{"name":5,"tags":24,"origin":34,"recommends":35,"description":7},[25,26,27,28,29,30,31,32,33],"short-form-video","tiktok","instagram-reels","account-growth","positioning","posting-cadence","trends","series","algorithm-2026","risco",[36,37,38,39,40,41,42,43],"video-shorts","shortform-ideation","shortform-packaging","shortform-editing","social-publisher","content-engine","brand-voice","analytics","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fshortform-strategy",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill shortform-strategy",{"tool":58,"command":59},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill shortform-strategy",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill shortform-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fshortform-strategy\u002FSKILL.md",true,[66,72,76,80],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"evals\u002Fcases.yaml","REFERENCE","参考文档",3462,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fshortform-strategy\u002Fevals\u002Fcases.yaml",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"evals\u002FREADME.md",737,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fshortform-strategy\u002Fevals\u002FREADME.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Flearning-loop-template.md",3093,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fshortform-strategy\u002Freferences\u002Flearning-loop-template.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fplatform-signals-2026.md",3848,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fshortform-strategy\u002Freferences\u002Fplatform-signals-2026.md",[85,93,98,105,112,119],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":94,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":92},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":92},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":92},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":92},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":92},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]