How do I install the Add Content skill?

Run npx skillmds@latest add debs-obrien/add-content in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Add Content safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Content?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Add Content free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Add Content?

debs-obrien (@debs-obrien) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Add Content by debs-obrien — Agent Skill

Name: Add Content
Author: debs-obrien

Add Content

Adds videos, blog posts, or podcasts to the debbie.codes website by extracting metadata from a URL, creating a content file with frontmatter, and opening a PR. Use when the user says 'add video', 'add blog post', 'add podcast', 'add this to the site', or provides a YouTube, podcast, or blog URL to add as content.

debs-obrien 38d8ab6 5 files · 12.9 KB Updated Sep 17, 2026

File contents

Add Content to debbie.codes

Fully automated workflow: URL → metadata extraction → file creation → PR (with deploy preview).

Determine content type

Identify from the user's request or URL:

YouTube URL (youtube.com/watch, youtu.be/) → Video. Read references/video.md
Podcast platform URL (e.g., Spotify, Apple Podcasts, podcast website) → Podcast. Read references/podcast.md
Blog platform URL (e.g., dev.to, hashnode, medium, or any article) → Blog. Read references/blog.md

If ambiguous, ask the user which content type to create.

Core workflow

Read references/environment.md for shell setup, git, and PR creation details.

1. Get the URL

Ask the user for the content URL if not provided.

2. Extract metadata via browser

Open the URL with playwright-cli
Handle any cookie consent dialogs
Take snapshots and read the snapshot YAML files to extract metadata
Do NOT invent or fabricate any metadata — all info must come from the page
If the publish date is not visible, ask the user
Close the browser when done

3. Validate tags

Only use tags that already exist in the corresponding content directory. Check with:

grep -h "^tags:" content/<type>/*.md | sed 's/tags: \[//;s/\]//;s/, /\n/g' | sed 's/^ *//' | sort -u

Do NOT create new tags. If no existing tags seem appropriate:

Prefer the closest matching existing tags that reasonably describe the content, or
Ask the user to choose from the existing tags you listed. If the user insists on new tags, explain that updating the tag taxonomy is outside this automated workflow and they should adjust it manually.

4. Create git branch

git stash
git checkout main && git pull origin main
git checkout -b add-<type>/<kebab-case-short-title>
git stash pop

5. Create the markdown file

Create in the appropriate content/<type>/ directory with a kebab-case filename. Follow the exact frontmatter schema from the content-type reference file.

6. Create PR

Commit only the content file, push, and create a PR. The PR will generate a deploy preview automatically — no need to run a local dev server. See references/environment.md for details.

---name: add-contentdescription: Adds videos, blog posts, or podcasts to the debbie.codes website by extracting metadata from a URL, creating a content file with frontmatter, and opening a PR. Use when the user says 'add video', 'add blog post', 'add podcast', 'add this to the site', or provides a YouTube, podcast, or blog URL to add as content.---# Add Content to debbie.codesFully automated workflow: URL → metadata extraction → file creation → PR (with deploy preview).## Determine content typeIdentify from the user's request or URL:- **YouTube URL** (`youtube.com/watch`, `youtu.be/`) → Video. Read [references/video.md](references/video.md)- **Podcast platform URL** (e.g., Spotify, Apple Podcasts, podcast website) → Podcast. Read [references/podcast.md](references/podcast.md)- **Blog platform URL** (e.g., dev.to, hashnode, medium, or any article) → Blog. Read [references/blog.md](references/blog.md)If ambiguous, ask the user which content type to create.## Core workflowRead [references/environment.md](references/environment.md) for shell setup, git, and PR creation details.### 1. Get the URLAsk the user for the content URL if not provided.### 2. Extract metadata via browser- Open the URL with `playwright-cli`- Handle any cookie consent dialogs- Take snapshots and read the snapshot YAML files to extract metadata- Do NOT invent or fabricate any metadata — all info must come from the page- If the publish date is not visible, ask the user- Close the browser when done### 3. Validate tagsOnly use tags that already exist in the corresponding content directory. Check with:```bashgrep -h "^tags:" content/<type>/*.md | sed 's/tags: \[//;s/\]//;s/, /\n/g' | sed 's/^ *//' | sort -u```Do NOT create new tags. If no existing tags seem appropriate:- Prefer the closest matching existing tags that reasonably describe the content, or- Ask the user to choose from the existing tags you listed.If the user insists on new tags, explain that updating the tag taxonomy is outside this automated workflow and they should adjust it manually.### 4. Create git branch```bashgit stashgit checkout main && git pull origin maingit checkout -b add-<type>/<kebab-case-short-title>git stash pop```### 5. Create the markdown fileCreate in the appropriate `content/<type>/` directory with a kebab-case filename. Follow the exact frontmatter schema from the content-type reference file.### 6. Create PRCommit only the content file, push, and create a PR. The PR will generate a deploy preview automatically — no need to run a local dev server. See [references/environment.md](references/environment.md) for details.

Frequently asked questions