pshreyas77/hermes-railway/telegram-to-obsidian-capture

Claude Code and agent skill by pshreyas77/hermes-railway

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Convert messy Telegram messages, voice transcriptions, URLs, PDFs, screenshots, and pasted conversations into Obsidian-ready notes with titles, summaries, source trails, tasks, wikilinks, and tags. Use when the Hermes and Telegram workflow receives raw captures for the vault.

Install

npx vskill@latest install pshreyas77/hermes-railway/telegram-to-obsidian-capture

SKILL.md

Telegram To Obsidian Capture

Overview

Turn quick phone captures into useful Obsidian notes. Preserve the raw input, extract what matters, file it into the right vault location, and respond with a short confirmation the user can read on Telegram.

Capture Contract

For every capture, produce one of these outcomes:

  • Create a new source note.
  • Create or update an existing project note.
  • Create one or more atomic notes linked to a source.
  • Place the capture in inbox with a clear question when classification is impossible.

Workflow

  1. Read the incoming Telegram material.
  2. Identify the capture type:
  • Quick idea
  • Link
  • PDF/document
  • Voice transcription
  • Pasted conversation
  • Instruction or task
  1. Preserve provenance:
  • Source should say telegram.
  • Include the URL, file name, sender context, or pasted-conversation label when available.
  1. Create the note:
  • Use clear filenames.
  • Use Obsidian-compatible Markdown.
  • Add frontmatter.
  • Add wikilinks to existing concepts when obvious.
  1. Update related notes:
  • Add to a project note if the capture changes active work.
  • Add to a map if the topic is recurring.
  1. Reply briefly on Telegram:
  • What note was created or updated.
  • Where it was filed.
  • Any follow-up question.

Output Standard

New capture notes should include:

yaml
---
type: source
status: inbox
created: YYYY-MM-DD
source: telegram
tags:
- source/telegram
---

Then:

  • Summary
  • Key points
  • Raw capture
  • Extracted notes or links
  • Follow-ups

Guardrails

  • Do not pretend to read a PDF, webpage, screenshot, or audio file if its contents were not actually available.
  • Do not over-organize tiny captures. A one-line idea can stay as a short note.
  • Do not create fake backlinks.
  • Do not expose sensitive Telegram content in public-facing outputs.
  • Ask one concise follow-up question if the capture cannot be filed responsibly.

Resources

  • Read references/capture-contract.md for detailed examples and response formats.
  • Use assets/prompt-cards.md when the user wants ready-to-send Telegram prompts.

Completion Criteria

Finish when the capture is saved as useful Markdown, linked where appropriate, and the user receives a short confirmation that makes the vault location obvious.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/pshreyas77/hermes-railway/telegram-to-obsidian-capture/badge)](https://verified-skill.com/skills/pshreyas77/hermes-railway/telegram-to-obsidian-capture)

Something wrong with this skill or its page? Tell us.