35 Claude Code skills on GitHub: claude-video, WRITING.md, paper2code, skill-doctor, skills-manage
Treat skills as reusable operating procedures: domain knowledge, writing standards, review methods, and project workflows that agents can apply repeatedly.
Github Awesome16 minTranscript found
Quick learning frame
Read this before watching.
AI strategy is choosing where agents create durable leverage, then managing scope, adoption, risk, and measurable outcomes.
This expands the atlas from single prompts into a durable skills library for better agent behavior.
Skill you build: Building a working mental map of the Claude Code skills ecosystem so you can pick the right installable skill for a given agent problem (UI generation, doc writing, token management, code review, sprite pipelines) instead of prompting from scratch.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Use Case
02Workflow
03Agent Role
04Metric
05Risk
06Adoption
Deep lesson
Turn this video into working knowledge.
2,180 cleaned transcript words reviewed across 819 timed caption segments.
Thesis
35 Claude Code skills on GitHub: claude-video, WRITING.md, paper2code, skill-doctor, skills-manage teaches a practical ai strategy move: Treat skills as reusable operating procedures: domain knowledge, writing standards, review methods, and project workflows that agents can apply repeatedly.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:55
Extending Claude's senses
“conclusion. Senior developer voice enforced by a text file. Claude code builds functional UIs that all look identical by default. The fancy AI official skills repository is a focused pack of agent skills for premium UI generation. Load...”
claude-video shows how a custom skill can give an agent a capability it lacks natively: it downloads a video, auto-scales frame extraction, pulls the timestamped transcript, and hands all of it to Claude so the model effectively 'watches' the video before answering. Install claude-video, feed it a YouTube link, and inspect what artifacts (frames, transcript) it produces to understand how a skill bridges a model's modality gap.
4:21
Rules-as-text skills
“skills, GitHub import wizard, and a discover scanner that finds project-level skills hiding on your machine. If you want your Claude code CLI to act less like a chat window and more like a 24/7 operating system, you...”
Several skills (Writing.md, the fancy AI UI pack, paper2code) work by dropping a single rule file or focused pack into your project to steer the agent's behavior, e.g. Writing.md forces concise human phrasing and bans filler like 'delve into' and 'crucial'. Add a Writing.md rule file to one project root and compare the AI's output prose before and after to feel how a plain text file enforces a senior-developer voice.
12:40
Skill governance and sync
“own prompts for maximum accuracy. Language-specific tools like the Moonbit best practices plugin stop agents from hallucinating niche syntax. Third Brain V5 skills is a Claude code skill collection to power them. High-level architectural skills, cost-aware LLM pipeline...”
As skill count grows, meta-skills appear: skill-doctor scans your skills directory locally for overlapping prompts, conflicting priorities, and security risks, while skills-manager uses a central directory plus symlinks to deploy skills to 27 platforms at once. Run skill-doctor against your installed skills to find redundancies and conflicts, then consider centralizing them with a symlink-based manager to keep rules synced across tools.
01
Use Case
Start with this video's job: Treat skills as reusable operating procedures: domain knowledge, writing standards, review methods, and project workflows that agents can apply repeatedly. Treat "Use Case" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:55, where the video says: “conclusion. Senior developer voice enforced by a text file. Claude code builds functional UIs that all look identical by default. The fancy AI official skills repository is a focused pack of agent skills for premium UI generation. Load...”
02
Workflow
Use "Workflow" to locate the part of the ai strategy workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 4:21, where the video says: “skills, GitHub import wizard, and a discover scanner that finds project-level skills hiding on your machine. If you want your Claude code CLI to act less like a chat window and more like a 24/7 operating system, you...”
03
Agent Role
Turn "Agent Role" into the reusable artifact for this lesson: A one-page business case for one agent workflow. This is where watching becomes something you can inspect and reuse.
04
Metric
Use "Metric" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Risk
Use "Risk" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Adoption
Use "Adoption" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a one-page business case for one agent workflow..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: Treat skills as reusable operating procedures: domain knowledge, writing standards, review methods, and project workflows that agents can apply repeatedly.
02
Explain the practical stakes without hype: This expands the atlas from single prompts into a durable skills library for better agent behavior.
03
Map the idea onto the Use Case -> Workflow -> Agent Role -> Metric -> Risk -> Adoption sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A one-page business case for one agent workflow.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: 35 Claude Code skills on GitHub: claude-video, WRITING.md, paper2code, skill-doctor, skills-manage
- URL: https://www.youtube.com/watch?v=48-lCMO4sQY
- Topic: AI Strategy
- My current learning frame: Pick three skills described in this video that target distinct problems (e.g. claude-video for modality, Writing.md for prose, skill-doctor for hygiene), install them, and document for each one what input it takes and what concrete output or behavior change it produces.
- Why this matters: This expands the atlas from single prompts into a durable skills library for better agent behavior.
Transcript anchors from this exact video:
- 0:55 / Evidence 1: "conclusion. Senior developer voice enforced by a text file. Claude code builds functional UIs that all look identical by default. The fancy AI official skills repository is a focused pack of agent skills for premium UI generation. Load..."
- 2:37 / Evidence 2: "grade new drafts, infographic and thumbnail creation. Your content system built around your actual voice. Most Claude code prompts are kitchen sink files that give the AI too much room to overthink. Matt Pocock's skills repo is the..."
- 4:21 / Evidence 3: "skills, GitHub import wizard, and a discover scanner that finds project-level skills hiding on your machine. If you want your Claude code CLI to act less like a chat window and more like a 24/7 operating system, you..."
- 8:42 / Evidence 4: "and transpiles them directly into modular Swift UI views, mapping design tokens to your existing Xcode asset catalog and custom view modifiers instead of hardcoding hex colors and absolute font sizes. One AI agent making a major architectural..."
- 10:19 / Evidence 5: "Claude code. PRD creation, rigorous code reviews, step-by-step implementation checks. The entire software development life cycle covered. Install via NPX or GitHub CLI and your agent inherits battle-tested workflows immediately. Hitting a rate limit mid-refactor and losing all..."
- 12:40 / Evidence 6: "own prompts for maximum accuracy. Language-specific tools like the Moonbit best practices plugin stop agents from hallucinating niche syntax. Third Brain V5 skills is a Claude code skill collection to power them. High-level architectural skills, cost-aware LLM pipeline..."
- 14:41 / Evidence 7: "into Claude code that sends your code base to OpenAI Codex, Google Gemini, and open code in parallel. A true cross-lineage peer review. Each model independently reviews and hunts bugs. The main Claude agent cannot merge code until..."
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page business case for one agent workflow.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Use Case -> Workflow -> Agent Role -> Metric -> Risk -> Adoption
- 3 concrete examples that apply the video idea to real agentic work
- 2 failure modes the video helps prevent
- a checklist I can use the next time I run Codex or Claude
- one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "35 Claude Code skills on GitHub: claude-video, WRITING.md, paper2code, skill-doctor, skills-manage", not a generic AI Strategy essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
Every new AI tool deserves a trial.
Every tool has integration cost. Start from workflow pain, not novelty.
If an agent can do it once, it is automated.
Automation means repeatable, monitored, recoverable, and reviewable.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a one-page business case for one agent workflow..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
Claude can't natively watch videos, so what four things does the claude-video skill actually do to a YouTube link so the model can 'watch' it before answering?
How does the Writing.md skill change AI-written prose, and what specific filler words does it ban?
What does skill-doctor scan your skills directory for, and what design choice keeps your proprietary prompts private?
Source shelf
Use the video as a doorway, then verify with primary sources.
