Obsidian Workflows
Productivity skill, available on Zeplik
Obsidian Workflows is a ready-to-run productivity skill on Zeplik. base files), wikilinks, callouts, plugins, zettelkasten, Web Clipper templates. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The Obsidian Workflows skill loads automatically when your request matches it, or you can invoke it directly by typing /obsidian-workflows in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Obsidian Workflows skill can do
- Write complete .base files with views, filters, formulas, and summaries
- Author Obsidian Flavored Markdown including wikilinks, embeds, callouts, and properties
- Build importable Obsidian Web Clipper templates for specific sites or content types
- Map an existing Base schema to a Clipper template and validate page data sources
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Obsidian Workflows skill works
/obsidian-workflows
Umbrella skill for Obsidian: authoring Obsidian Flavored Markdown (wikilinks, embeds, callouts, properties), creating and editing Bases (.base files with views, filters, formulas, summaries), and building importable Obsidian Web Clipper templates. The body of this skill is a dispatch table; the depth lives in references/. Pick the reference(s) matching the user's intent, read them, then answer. There is no access to the user's vault: ask them to paste or upload the notes, .base files, or sample pages involved, and produce complete file contents they can save into their vault (full .md notes, full .base YAML, full Clipper JSON to import), plus the exact steps to perform in the Obsidian app.
Dispatch table
| Intent | Reference |
|---|---|
| Create or edit .base files: views (table/card/list), filters, formula properties, summaries, embedding Bases in notes | references/obsidian-bases.md |
| Obsidian Flavored Markdown syntax: wikilinks, embeds, callouts, properties/frontmatter, tags, footnotes, comments, math | references/obsidian-markdown.md |
| Build an Obsidian Web Clipper template (importable JSON) for a site or content type | references/obsidian-clipper-template-creator.md |
| Clipper template JSON structure | references/obsidian-clipper-template-creator--json-schema.md |
| Clipper variables (preset, schema.org, selector, meta) | references/obsidian-clipper-template-creator--variables.md |
| Clipper formatting filters | references/obsidian-clipper-template-creator--filters.md |
| Mapping an existing Base schema to a Clipper template | references/obsidian-clipper-template-creator--bases-workflow.md |
| Validating page data (schema.org, meta tags, selectors) for a Clipper template | references/obsidian-clipper-template-creator--analysis-workflow.md |
| Example importable Clipper templates | references/obsidian-clipper-template-creator--clipping-template.md, references/obsidian-clipper-template-creator--recipe-template.md |
How to work
- Identify the intent and read the matching reference file(s) before answering. Base syntax is exacting -- follow the reference rather than guessing at YAML keys or filter functions.
- Ask the user to paste what you cannot see: existing note frontmatter, a .base file to modify, or a sample URL/page for a Clipper template. Vault structure or plugin questions deserve one clarifying question about their setup before going deep.
- Deliver complete, savable artifacts: whole .md files, whole .base files in fenced yaml blocks, and Clipper templates as a single importable JSON code block. Include where to save the file in the vault and any app steps (enable core plugin, import template) as a numbered list.
- Where a reference assumes direct file-system access to the vault, translate that to: ask for pasted content, return finished files.
- Redirect out-of-lane requests: Notion databases and templates go to notion-workflows.
Usage
/obsidian-workflows $ARGUMENTS
How to use the Obsidian Workflows skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Obsidian Workflows skill right away.
Describe your productivity task
Ask in plain language, or type /obsidian-workflows to invoke the skill directly. Zeplik recognizes the Obsidian Workflows skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- anthropic
- License
- MIT
Adapted from the open-source davila7/claude-code-templates project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Obsidian Workflows skill?
- Obsidian Workflows is a ready-to-run productivity skill on Zeplik. base files), wikilinks, callouts, plugins, zettelkasten, Web Clipper templates. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use Obsidian Workflows on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /obsidian-workflows in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Obsidian Workflows skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Obsidian Workflows skill runs on your preferred model for the task.
- Where does the Obsidian Workflows skill come from?
- The Obsidian Workflows skill is adapted from the open-source davila7/claude-code-templates project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Obsidian Workflows skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related productivity skills
- Audio TranscriberUse when the user attaches audio or voice recordings to transcribe -- cleanup, speaker labels, timestamps, minutes or notes from a recording. Not for summarizing documents (use summarize-anything).
- Deadline PrepUse when a demo, standup, or delivery deadline looms: turn git history and notes into a structured demo outline. Not for sprint ceremonies (use sprint-planning) or capacity math (use capacity-plan).
- File OrganizerUse when designing a folder structure and reorganization plan for messy files -- downloads cleanup, duplicates, naming, archive rules. Not for converting file formats (use file-conversion).
- Linear Issue AssistantUse when the user pastes Linear issues, CSV exports, or cycle data -- triage, well-formed issue writeups, cycle plans, updates in Linear conventions. Not for sprint ceremonies (use sprint-planning).
- Marp Slide DecksUse when creating Markdown/Marp slide decks with themed embedded CSS the user renders via Marp CLI or VS Code. Not for general presentation building (use slides).
- Notion WorkflowsUse when designing Notion databases, templates, formulas, or workspace systems -- knowledge capture, meeting docs, specs, template businesses. Not for generic note-taking advice.
More on Zeplik
Try Obsidian Workflows on Zeplik
Every model, one chat. Bring the Obsidian Workflows skill into your next conversation and let the assistant do the work.