Organise Contentstack assets with AI
Plan a useful structure for a shared asset library. Distinguish identical uploads from deliberate crops before making a cleanup decision in the DAM.
Organise Contentstack assets with AI around the questions your colleagues ask. “Where is the square crop with the new label?” is a better starting point than a request for a perfect folder tree. The answer may be a field that records the crop, rather than a new folder for every size.
The asset-management guide concerns the standalone Assets product. It explains how duplicate sets, file versions and workspaces behave there. Matching photographs by eye is a different task from finding identical files: two uploads may contain the same bytes and have entirely different names.
What it does
- Plan fields that make campaign assets easier to find
- Separate exact duplicates from intentional variants
- Understand the difference between a space and a workspace
- Review a suggested tag or alternative description
- Locate an earlier asset version without confusing it with a separate upload
Install and use
- Use the skill in a compatible agent and say whether you use Assets DAM or the library inside a CMS stack. You need an authorised account only to carry out changes in the product.
- Ask: “Retail and editorial teams use different crops of our packaging shots. Suggest metadata that distinguishes them without making another copy.”
- Try the scheme on a handful of files. Before deleting an apparent duplicate, check the intended version and where the asset is used.
FAQ
Source
Made by Contentstack. Original skill: asset-management, published on GitHub under the MIT licence.
View on GitHub