skills.rest
yoshisada
yoshisadaCOMMUNITY
Explore all skills by this author →
GitHub

shelf-feedback

Read Obsidian dashboard feedback, suggest actions, and archive items with timestamps.

Updated Mar 26, 2026
Search Tags:#workflow#feedback#mcp#dashboard#obsidian#archiving
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill shelf-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shelf-feedback
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-shelf/skills/shelf-feedback
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill shelf-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read and process feedback from the Obsidian project dashboard. Displays items with suggested actions, then archives processed items to the Feedback Log with timestamps. Run at session start to pick up notes left in Obsidian.

Core Features & Use Cases

  • Surface feedback items from the Obsidian dashboard's ## Feedback section and present a recommended action per item.
  • Archive processed items to the ## Feedback Log with a timestamp, preserving other dashboard sections.
  • Work at session start to capture notes left in Obsidian and keep a clean Feedback Log synchronized with a live dashboard.

Quick Start

Run shelf-feedback at session start to surface items from the Obsidian dashboard and archive them to the Feedback Log with timestamps.

Frequently Asked Questions about shelf-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I surface and archive Obsidian dashboard feedback automatically?▼

Obsidian dashboard feedback is processed at session start by reading the ## Feedback section via MCP, suggesting an action per item, and archiving them to the ## Feedback Log with timestamps.

Do I need an MCP backend to read and update an Obsidian dashboard?▼

Yes, a connected MCP backend is required to safely perform read-then-write operations when updating the Obsidian dashboard and archiving feedback items to the Feedback Log.

How does the system identify my project when processing Obsidian feedback?▼

Project identity is derived automatically from the .shelf-config file or the git remote configuration, allowing the feedback workflow to correctly associate dashboard notes with your project.

What happens to other dashboard sections when feedback is archived to the Feedback Log?▼

Other Obsidian dashboard sections are preserved untouched when feedback items are archived to the Feedback Log, ensuring only the ## Feedback section is cleared while the rest of the dashboard remains intact.

When should I run the Obsidian feedback workflow to capture notes?▼

Run the feedback workflow at session start to capture notes left in Obsidian, ensuring your dashboard stays clean and the Feedback Log remains synchronized with recent project activity.

Can I use this workflow without a .shelf-config file or git remote?▼

The workflow relies on deriving project identity from either a .shelf-config file or a git remote, so at least one of these must be present to process and archive Obsidian feedback correctly.

Related Skills

Explore More Content & Communication Skills→
Knuckles-TeamKnuckles-Team
2

git-config

Read, set, and validate Git config values across global and local scopes.

Official
Intermediate
semicolon-devteamsemicolon-devteam

summarize-meeting

Summarize STT transcripts and meeting notes into discussion and decision summaries.

Official
Advanced
justinsenseijustinsensei
1

obsidian-ingest-log

Log new Obsidian vault inputs and update project notes via Python scripts.

Community
Advanced
epieczkoepieczko

audit.log

Log Betty Framework skill executions as timestamped JSON audit entries.

Community
Basic