The user maintains \"Bases\" in Bases/*.base which define the schema and properties for different types of notes (e.g., Recipes, Clippings, People). Identify the
The Bases Workflow skill helps structure and standardize note-taking by leveraging predefined schema templates called “Bases” stored in `Bases/*.base` files. Each Base defines the properties required for different content types like Recipes, Clippings, or People, enabling consistent metadata capture across notes. This approach streamlines how information is clipped, organized, and later retrieved, aligning frontmatter properties with specific content categories.
This skill is designed for content strategists and knowledge managers who maintain large, categorized note collections, such as SEO specialists organizing research articles or social media managers curating campaign assets. It also suits technical operators setting up automated clipping workflows that require strict schema adherence for notes, ensuring clean data for performance tracking or content audits.
Begin by identifying the content category to clip, such as a Recipe or News Article. Next, locate the corresponding `.base` file within the `Bases/` directory—for example, `Bases/Recipes.base` for recipes or `Bases/Clippings.base` for generic articles. Then, read the Base file to understand the required properties under its YAML-like `properties` section. Finally, map these Base properties to the clipper’s JSON `properties` array, deciding which fields should be auto-filled, hardcoded, or left blank for manual input.
How do I know which Base file to use? Choose the Base file that best matches the content type you want to clip, based on the folder naming and property definitions. Can properties be auto-filled? Yes, some properties like `author` or `published` can be automatically extracted, while others may require manual entry or fixed values. What if my content type doesn’t have a Base? You can create a new `.base` file defining the schema needed to maintain consistency across your notes.
Attach the Bases Workflow skill to a Metaflow agent task that handles content clipping or note creation. The agent will use the `.base` files to enforce schema adherence, automatically map properties, and prompt for any missing data during the workflow. Expect structured frontmatter and consistent metadata output that improves downstream content management and analysis. This setup integrates seamlessly with your existing Metaflow pipelines and...
For broader context, see our roundup of claude skills for marketing, and read Claude skills for SEO for related setup guidance.