smithery.ai

inventory-content

Systematic cataloging of information assets. Creates comprehensive inventories of all content with metadata and characteristics.

First seen Mar 24, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,484 B
  • docs SUMMARY.md 153 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Content Inventory Skill

Create a systematic catalog of information assets within a specified path. This skill builds a comprehensive inventory including metadata, file characteristics, and format analysis to support content governance and strategic planning.

Inputs

  • PATH - The directory or file path to inventory (e.g., "/documentation")
  • OUTPUT_FORMAT - (Optional) The output format for the inventory, e.g., "csv", "json", "markdown" (default: "json")
  • METADATA_EXTRACTION - (Optional) Boolean, whether to extract deep metadata (author, date, tags) (default: true)
  • FORMAT_ANALYSIS - (Optional) Boolean, whether to analyze file formats and types (default: true)

Workflow

Step 1: Asset Discovery

Recursively scan the PATH to identify all files and assets.

  • Record file paths, names, and sizes.
  • Identify file types (Markdown, HTML, PDF, Image, etc.).

Step 2: Metadata Extraction

If METADATA_EXTRACTION is true, extract metadata from each asset:

  • System Metadata: Creation date, modification date, owner.
  • Embedded Metadata: Frontmatter (YAML), title headers, tags, categories.
  • Content Metrics: Word count, reading time estimation.

Step 3: Format & Structure Analysis

If FORMAT_ANALYSIS is true, analyze the structure:

  • Template Usage: Identify if standard templates are used.
  • Hierarchy Depth: Depth in the directory structure.
  • Resource Dependencies: Images or other assets linked.

Step 4: Inventory Report Generation

Compile the data into a structured inventory format (CSV, JSON, or Markdown Table) as specified by OUTPUT_FORMAT.

Required Outputs

A CONTENTINVENTORYREPORT in the specified OUTPUT_FORMAT containing:

  • Asset List: Full list of discovered assets.
  • Metadata Table: Columns for Title, URL/Path, Author, Last Modified, Type, Tags.
  • Summary Statistics: Total count by type, average age, volume by category.

Quick Reference

  • Purpose: Establish a baseline understanding of content assets for governance.
  • Use Case: Migration planning, audit preparation, consolidation projects.