‹ 首页

design-metadata-schema

@dandye · 收录于 5 天前 · 上游提交 3 个月前

Design comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.

场景内容分类信息架构

适合你，如果需要为内容或资产设计结构化的元数据方案

/ 下载安装
https://github.com/dandye/ai-runbooks/tree/main/skills/design-metadata-schema ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add dandye/ai-runbooks/design-metadata-schema
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- dandye/ai-runbooks/design-metadata-schema
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify dandye/ai-runbooks/design-metadata-schema
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
119GitHub stars
~433上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 086cbf6 · 表述以原文为准
它做什么

安装后，Claude 能为内容定义结构化字段、验证规则和标准映射，生成 JSON Schema、XML 或 Markdown 格式的元数据模板。

什么时候触发

当用户需要为某个内容域（如 /content）设计元数据框架，或要求定义字段、验证规则、符合 Dublin Core 等标准时触发。

装好后可以这样说
会生成字段字典、验证逻辑和标准映射。
模板包含标准字段和业务特定字段。
技能原文 SKILL.md作者撰写 · Apache-2.0 · 086cbf6

Design Metadata Schema Skill

Develop a comprehensive metadata schema for content management. This skill defines structured fields, validation rules, and standards compliance to improve searchability and management.

Inputs
  • PATH - The content domain to apply the schema to (e.g., "/content")
  • OUTPUT_FORMAT - (Optional) The output format for the schema, e.g., "json-schema", "xml", "markdown" (default: "json-schema")
  • DUBLIN_CORE - (Optional) Boolean, whether to align with Dublin Core standards (default: true)
  • CUSTOM_FIELDS - (Optional) List of custom business-specific fields to include
  • VALIDATION_RULES - (Optional) Boolean, whether to define validation logic for fields (default: true)
Workflow
Step 1: Requirement Analysis

Analyze the content types at PATH to determine metadata needs.

  • Identify common attributes (Title, Date, Author).
  • Identify specific attributes (Product ID, Version, Region).
Step 2: Schema Definition

Define the fields and their properties.

  • Standard Fields: Map to Dublin Core (Title, Creator, Subject, etc.) if enabled.
  • Custom Fields: Define fields specified in CUSTOM_FIELDS or discovered during analysis.
Step 3: Constraints & Validation

If VALIDATION_RULES is true, define:

  • Data Types: String, Date, Integer, Boolean, Enum.
  • Required/Optional: Cardinality constraints.
  • Controlled Vocabularies: Allowed values for specific fields.
Step 4: Schema Output

Generate the schema definition in the requested OUTPUT_FORMAT (e.g., JSON Schema, XML Schema, or Markdown Table).

Required Outputs

A METADATA_SCHEMA object in the specified OUTPUT_FORMAT containing:

  • Field Dictionary: Name, Description, Type, Multiplicity.
  • Validation Logic: Rules for data entry.
  • Mapping: Correspondence to standards (like Dublin Core).
Quick Reference
  • Purpose: Standardize content tagging for consistency and interoperability.
  • Standards: Dublin Core, Schema.org.
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…