asset-intake-checklist

Normalize new resources into an asset/resource library with intake metadata, naming, storage, ownership, and follow-up checks. Use when onboarding files, links, templates, datasets, documents, or reusable components into a shared library and the task asks for intake, registration, cataloging, asset onboarding, metadata completion, naming cleanup, or repository/resource-library entry.

Use this skill to turn an informal resource into a registered library asset.

Core workflow

1. Identify the resource type: file, link, template, dataset, document, script, image, or reusable component.
2. Capture required metadata before filing:
   • title
   • short description
   • owner or source
   • license or usage restriction
   • version or date
   • keywords/topics
   • target library path or collection
3. Normalize the name. Prefer lowercase kebab-case for folders/files when the library allows it; otherwise follow the destination convention.
4. Place the resource in the target collection. Keep a stable path and avoid duplicate copies.
5. Record the entry in the library index, manifest, registry, or catalog used by that library.
6. Verify the entry can be found by name, keyword, and path.
7. Flag missing license, owner, or sensitivity information instead of guessing.

Output checklist

Return or record:

• asset title
• canonical location/link
• resource type
• owner/source
• license/usage constraints
• version/date
• keywords
• verification result
• open follow-ups, if any

When to stop and ask

Ask before publishing externally or overwriting an existing asset when:

• license or redistribution rights are unclear
• the resource contains private, secret, or personal data
• the destination already has a similar asset and deduplication is ambiguous
• the requested action deletes, moves, or replaces the only copy

References

• For metadata field examples and common intake patterns, read references/intake-fields.md.