obsidian-user-input

Sub-skill of obsidian: User Input.

5 stars

Best use case

obsidian-user-input is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of obsidian: User Input.

Teams using obsidian-user-input should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/user-input/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/business/productivity/obsidian/user-input/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/user-input/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How obsidian-user-input Compares

Feature / Agent	obsidian-user-input	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Sub-skill of obsidian: User Input.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# User Input

## User Input


<% tp.system.prompt("Enter project name") %>
<% tp.system.suggester(["Option 1", "Option 2"], ["value1", "value2"]) %>

Related Skills

user-approved-plan-state-sync

from vamseeachanta/workspace-hub

Reconcile GitHub and local repo state when a plan has been user-approved, including direct approval messages that require creating the local marker and moving the issue to status:plan-approved.