--- name: li-repurpose description: >- Turn one long asset - a YouTube video, podcast, newsletter, blog post, transcript or client call - into a week of LinkedIn posts. Use when the user says "repurpose this", "turn this into posts", "I have a video/newsletter/ transcript", or pastes a long piece of content and wants it on LinkedIn. title: li-repurpose canonical_url: https://skilld.dev/gh/jakeschincariol/linkedin-agent-skill/li-repurpose last_updated: 2026-09-16T18:45:38.000Z --- > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/linkedin-agent-skill/li-repurpose`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/li-repurpose`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/jakeschincariol/linkedin-agent-skill/li-repurpose) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/li-repurpose`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/li-repurpose --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/li-repurpose --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # li-repurpose One good long asset contains four to six posts. Most people extract one and throw the rest away. ## Input A transcript, an article, a newsletter, a script, a call summary. If the user gives a YouTube URL and there is a transcript tool available in the session, use it; otherwise ask them to paste the text. Read the whole thing before extracting anything. ## Extract, do not summarise A summary of a video is not a post. Nobody wants the summary. Go through the asset and pull out the things that stand alone: | pull | what it is | | --- | --- | | **Claims** | every sentence that would start an argument | | **Numbers** | every figure, cost, duration, percentage | | **Stories** | every moment with a person, a scene and a cost | | **Mechanisms** | every "the way this works is..." explanation | | **Mistakes** | every admission of something that went wrong | | **Lines** | every sentence that is already quotable as-is | List what you found, with counts, before writing anything. If the asset yields fewer than four items, it is thin, and four posts squeezed out of it will be thin too. Say that. ## Then build the week Each extract becomes one post, and each post has to stand completely on its own - the reader has not seen the video and never will. Never write "as I mentioned in my latest video". The post is the thing. Assign a hook formula from `li-post/hooks.json` to each, and vary them: five posts from one source with the same hook shape reads as a content mill. Order them across the week so the strongest claim goes first, the story goes midweek, and the mechanism post goes last, when people who liked the earlier ones are watching for it. ## Output ``` SOURCE: "Why we killed discovery calls" (18 min, 3,400 words) FOUND 4 claims, 6 numbers, 2 stories, 3 mechanisms, 1 mistake, 5 quotable lines WEEK TUE #1 Contrarian Discovery calls are a tax you pay for a bad website WED #17 Time Anchor We got 6 hours a week back by deleting one calendar link THU #9 Cold Open "Can we just hop on a quick call?" FRI #21 Direct Value The 4-question form that replaced the call. Steal it. Say "write Tuesday" and I will draft it. ``` Then draft on request, one at a time, each through `/li-post` and `/li-human`. Do not dump four finished posts at once - they will all sound the same, and the user will edit none of them.