One-click install
npx skills add https://github.com/tarang-tj/syllabus-ai --skill ckm-assets-organizing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckm:assets-organizing
Source: https://github.com/tarang-tj/syllabus-ai/tree/main/.claude/skills/assets-organizing
Command: npx skills add https://github.com/tarang-tj/syllabus-ai --skill ckm-assets-organizing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organize and standardize asset outputs across multiple channels and projects to reduce chaos and mislabeling.

Core Features & Use Cases

  • Standard Output Paths: predefined, kebab-case directories and file names for all asset types (articles, videos, banners, designs, transcripts).
  • Centralized Reference: links to naming conventions and directory structure guidelines to ensure consistency across teams.
  • Scalable Organization: supports scripts/references/assets to extend and enforce structure across campaigns.

Quick Start

Create a new assets directory for your project and apply the standard kebab-case naming, date prefixes, and folder structure described in the references.

Frequently Asked Questions about ckm:assets-organizing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize content assets like articles and videos to avoid mislabeling across projects?

Organizing content assets requires standardizing output paths and enforcing kebab-case naming conventions. This skill applies date prefixes and self-contained folder structures to articles, videos, and designs, reducing chaos and mislabeling across multiple channels and projects.

What's the best way to structure directories for content production workflows?

The best way to structure directories for content production is using self-contained folders with predefined output paths. This approach enforces consistent directory structures and centralizes guidelines, ensuring scalable organization across various campaigns and asset types.

When do I need kebab-case naming conventions for asset management?

You need kebab-case naming conventions for asset management when standardizing file outputs across multiple channels. Applying kebab-case with date prefixes ensures consistent file names for articles, videos, banners, and designs, preventing mislabeling and maintaining centralized reference guidelines.

Can I use a standard folder structure for multiple asset types like banners and transcripts?

Yes, you can use a standard folder structure for multiple asset types. The system supports predefined directories and kebab-case file names for articles, videos, banners, designs, and transcripts, ensuring consistent output paths and scalable organization across campaigns.

How do I start applying naming conventions and directory structures to a new assets directory?

To start applying naming conventions, create a new assets directory for your project. Then apply the standard kebab-case naming, date prefixes, and folder structure described in the centralized reference guidelines to ensure consistent output paths across all asset types.

Does this approach support extending directory structure guidelines across different campaigns?

Yes, this approach supports extending directory structure guidelines across different campaigns. It provides scalable organization through scripts and references, allowing you to enforce consistent naming conventions and folder structures across various projects and channels.