agentleFS
eugenezhangco-speceugenezhangco-spec/athena/.claude/skills/video-ideas/SKILL.md

video-ideas

Skill0 starsChanged 7 months agoMITView on GitHub

Capture video content ideas into the user's Notion Video Ideas database. Track from Draft to Ready to Published. Use when the user mentions a video idea, content concept, or says "video idea", "add to video ideas", "content idea", "I should film", "that would make a good video".

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If not present, ask the user to set it up or suggest running the onboard skill.

    line 25
  2. Distinctive:

    Write a clear, compelling title for the Name field (how it would read in a content calendar).

    line 41
  3. Distinctive:

    If the user shared a URL that inspired the idea, capture it in Source URL.

    line 42
  4. Distinctive:

    If the user provides extra context (hook, angle, target audience, key points), add it as page body content.

    line 44
  5. Very specific:

    Create the entry via mcp__notion__notion-create-pages.

    line 45
  6. Distinctive:

    Default Status is "Draft" unless the user says it is ready to film.

    line 50
  7. Distinctive:

    If the idea connects to an existing content series or goal, note that in the page body.

    line 52
  8. Distinctive:

    If the user brainstorms multiple ideas at once, save each as a separate entry.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Video Ideas

When to Use

  • User mentions a video idea, content concept, or filming plan
  • User says "video idea", "add to video ideas", "content idea", "I should film", "that would make a good video"
  • User shares a link that inspires a video concept
  • During day planning or content brainstorms

Prerequisites

Writes to a Notion database. The user must have configured in personal/notion-databases.md:

video_ideas_database_id: <user's Notion database ID>
video_ideas_data_source: collection://<data source id>
video_ideas_parent_page: <parent page id>

If not present, ask the user to set it up or suggest running the onboard skill.

Expected Notion Schema

PropertyTypeOptions
NametitleThe video concept
DatedateAuto-set to today
Source URLurlOptional — inspiration link
StatusselectDraft, Ready, Published, Skipped

Adapt to the user's actual property names if they differ.

Steps

  1. Extract the video concept from the user's message.
  2. Write a clear, compelling title for the Name field (how it would read in a content calendar).
  3. If the user shared a URL that inspired the idea, capture it in Source URL.
  4. Set Date to today. Set Status to "Draft".
  5. If the user provides extra context (hook, angle, target audience, key points), add it as page body content.
  6. Create the entry via mcp__notion__notion-create-pages.
  7. Confirm back with the saved title.

Rules

  • Default Status is "Draft" unless the user says it is ready to film.
  • Titles should be punchy and descriptive. Think YouTube/Short titles, not internal notes.
  • If the idea connects to an existing content series or goal, note that in the page body.
  • Green tier — save first, confirm after.
  • If the user brainstorms multiple ideas at once, save each as a separate entry.

Output Format

Saved to Video Ideas:
- [Name] (Status)

One line per entry. If a Source URL was captured, append "(from [domain])".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.