Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Creator Video

ASecurity

Plan and script a short video presented by a person on camera. Use for founder demos, talking-head explainers, creator tutorials, launch clips, and shot lists.

214 stars
0 votes
1 copies
1 views
Added 10/1/2026
documentation

Works with

cli

Security Analysis

A100/100

Pro scans all 13 files and shows the line behind each finding

Scanned 10/1/2026

$npx -y skills add NeverSight/skills_feed --skill creator-video --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Creator Video?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Creator Video
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/neversight-creator-video/badge)](https://www.skillsdirectory.com/skills/neversight-creator-video)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: creator-video
description: Plan and script a short video presented by a person on camera. Use for founder demos, talking-head explainers, creator tutorials, launch clips, and shot lists.
---

# Creator video

Build the video around a real task and a claim the viewer can see tested. The presenter is part of the proof: their actions, screen, and result should agree.

## Choose a shape

- **The test:** Show the same task two ways, measure the result, then inspect the output. Use when the claim can be checked on camera.
- **The real task:** Follow the presenter doing useful work with the product. Use when the value appears during the work itself.
- **The day:** Show a recurring problem and how the product changes it. Use when the environment and human context matter.
- **The guided screen:** Put the presenter beside a legible screen recording. Use when the interface is the main story.

Choose the shape that the available footage can prove. Do not invent a test result or stage work as spontaneous.

## Write the beat sheet

Start with the result, tension, or action. Introduce the presenter once the viewer has a reason to care. Write one row for each beat:

| Time | Camera or screen | Exact spoken line | Evidence shown |
|---|---|---|---|
| 0:00 | Task already under way | “Can I finish this before the timer?” | Timer and task are visible |

Keep each spoken line easy to say in one breath. Replace broad claims with a specific result or an honest demonstration. If the product has a material limitation or privacy setting, show the relevant control and explain its scope precisely.

Turn the beat sheet into a shot list: camera setups, screen captures, props, and any measurements needed. State what can be filmed now and what is still missing.

## Shoot and edit

- Record a clean voice track. Place the microphone close enough that the product and presenter remain intelligible on a phone.
- Keep the lens near eye level. Leave safe space for platform controls and captions.
- Capture screens directly at a readable resolution. Show the real product state, including loading or errors when they matter to the claim.
- Record each spoken beat twice: one precise take and one natural take.
- Cut pauses and repetition while preserving the sequence of actions. Do not edit a timed comparison in a way that changes its result.
- Use captions when they help silent viewing. Check that they do not hide the UI or contradict what was said.

Export the aspect ratios the user needs. Reframe each ratio deliberately; do not crop away the evidence. Choose a cover frame with a clear subject and legible result.

## Before delivery

Watch the final export with sound and once muted. Check that the opening is understandable, the screen is readable, any numbers match the footage, captions are accurate, and the call to action describes one clear next step.

Attribution

NeverSightNeverSight
View sourceSee grades on GitHubMore from NeverSight →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

Architecture Diagram Creator

Create comprehensive HTML architecture diagrams with data flows, business context, and system architecture.

6661 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in W...

1798860 votes
View all in documentation →