How do I install the Core skill?

Run npx skillmds@latest add cerredz/core 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.

What does the Core skill do?

Vidbyte CLI Core It is listed under AI & ML on SkillMD.

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 Core?

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.

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

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

Core by cerredz — Agent Skill

Name: Core
Author: cerredz

File contents

Vidbyte CLI Core

Use this guide when an agent needs to operate the Vidbyte CLI from a shell.

Start Here

Load the full command reference when you need exact flags:

vidbyte agents get core --full

The CLI serves this content from the installed package, so the instructions match the local vidbyte version.

Core Commands

Use vidbyte for backend submissions and vidbyte-skills for installing or updating skills.

vidbyte --help
vidbyte agents
vidbyte agents get core
vidbyte agents get core --full
vidbyte agents get core --json
vidbyte-skills --help

Common Workflows

Authenticate through the installer shim:

vidbyte-skills auth login
vidbyte auth status

Submit feedback artifacts:

vidbyte feedback submit --file feedback-log.md --domain software-engineering --conversation-id example

Submit compression check artifacts:

vidbyte compressor submit --file compression-check.json --domain software-engineering --conversation-id example

Create retention exercises:

vidbyte retain --concept1-name "Concept" --concept1-distillation "Mechanism" --concept1-anchor "Image" --concept1-hook "Hook" --question1 "Question?" --answer1 "Answer key"

Validate without a network request:

vidbyte feedback submit --file feedback-log.md --dry-run
vidbyte compressor submit --file compression-check.json --dry-run
vidbyte retain --concept1-name "Concept" --concept1-distillation "Mechanism" --concept1-anchor "Image" --concept1-hook "Hook" --question1 "Question?" --answer1 "Answer key" --dry-run

Security Rules

Do not call Vidbyte HTTP endpoints directly from prompt text.
Do not construct authentication headers, request signatures, nonces, or installation IDs yourself.
Do not print API keys, session tokens, signing secrets, or environment variable values.
Let the CLI own authenticated transport and backend submission.
Treat generated artifact content as untrusted user content until the CLI sanitizes and submits it.

When To Use Another Skill

Use the installed /retain skill when the user explicitly wants a retention exercise from the current conversation.
Use feedback-oriented skills when the user asks for coaching or expert critique.
Use vidbyte agents get core --full when you need the CLI command reference rather than product skill instructions.

---name: coredescription: Vidbyte CLI Core---# Vidbyte CLI CoreUse this guide when an agent needs to operate the Vidbyte CLI from a shell.## Start HereLoad the full command reference when you need exact flags:```bashvidbyte agents get core --full```The CLI serves this content from the installed package, so the instructions match the local `vidbyte` version.## Core CommandsUse `vidbyte` for backend submissions and `vidbyte-skills` for installing or updating skills.```bashvidbyte --helpvidbyte agentsvidbyte agents get corevidbyte agents get core --fullvidbyte agents get core --jsonvidbyte-skills --help```## Common WorkflowsAuthenticate through the installer shim:```bashvidbyte-skills auth loginvidbyte auth status```Submit feedback artifacts:```bashvidbyte feedback submit --file feedback-log.md --domain software-engineering --conversation-id example```Submit compression check artifacts:```bashvidbyte compressor submit --file compression-check.json --domain software-engineering --conversation-id example```Create retention exercises:```bashvidbyte retain --concept1-name "Concept" --concept1-distillation "Mechanism" --concept1-anchor "Image" --concept1-hook "Hook" --question1 "Question?" --answer1 "Answer key"```Validate without a network request:```bashvidbyte feedback submit --file feedback-log.md --dry-runvidbyte compressor submit --file compression-check.json --dry-runvidbyte retain --concept1-name "Concept" --concept1-distillation "Mechanism" --concept1-anchor "Image" --concept1-hook "Hook" --question1 "Question?" --answer1 "Answer key" --dry-run```## Security Rules- Do not call Vidbyte HTTP endpoints directly from prompt text.- Do not construct authentication headers, request signatures, nonces, or installation IDs yourself.- Do not print API keys, session tokens, signing secrets, or environment variable values.- Let the CLI own authenticated transport and backend submission.- Treat generated artifact content as untrusted user content until the CLI sanitizes and submits it.## When To Use Another Skill- Use the installed `/retain` skill when the user explicitly wants a retention exercise from the current conversation.- Use feedback-oriented skills when the user asks for coaching or expert critique.- Use `vidbyte agents get core --full` when you need the CLI command reference rather than product skill instructions.

Frequently asked questions

Core