agentleFS
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/okc-urlSpotify/SKILL.md

okc-urlSpotify

Skill0 starsChanged 44 days agoMITView on GitHub

Ingests a Spotify podcast episode using the Google Chrome DOM hydration bridge, extracts full synchronized transcript and metadata, curates raw note, compiles wiki concepts, and syncs vault.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When this skill is invoked via /okc-urlSpotify <url> (or when a Spotify URL is passed to /okc-urlPodcast), execute the following …

    line 9
  2. Very specific:

    Zero Extra Read Turns: If is_truncated is False, do not call read_file on temp/fetched_data.txt or temp/fetched_data.json.

    line 14
  3. Very specific:

    Update or create 1-3 core concepts for wiki/.

    line 24
  4. Very specific:

    Commit all notes in a single call using FastMCP commit_curated_note:

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spotify Podcast Curator Skill

When this skill is invoked via /okc-urlSpotify <url> (or when a Spotify URL is passed to /okc-urlPodcast), execute the following streamlined 2-step workflow:

  1. Fetch & Hydrate Spotify Transcript (Single-Turn FastMCP):
    • Execute the native FastMCP tool fetch_spotify_data(url="<url>") on the okc server (or fetch_podcast_data(url="<url>") which auto-delegates).
    • Mechanism: Connects to the user's active session in Google Chrome via AppleScript, activates the episode's "Transcript" tab, resolves React DOM virtualization through automated hydration scrolling, and returns inline full text (when is_truncated == False) + already_exists status + SQLite graphify_context.
    • Zero Extra Read Turns: If is_truncated is False, do not call read_file on temp/fetched_data.txt or temp/fetched_data.json.
  2. Synthesize & Atomically Commit (Hot-Path + Async Background Sync):
    • Format the episode into a structured Markdown note in the designated raw/ zone following vault conventions:
      • H1 title and source blockquote (Channel/Author, Date, Type: podcast, Processed: DD-MM-YYYY, Tags: #no-read-yet).
      • ## 📌 Key Takeaways (numbered list).
      • Thematic narrative sections with Mermaid diagrams where appropriate.
      • ## Flashcards (Q: ... / A: ...).
      • ## Glossary (**Term**: Definition).
      • ## Related (- [[...]]).
    • Update or create 1-3 core concepts for wiki/.
    • Commit all notes in a single call using FastMCP commit_curated_note:
      commit_curated_note(
          raw_note_path="Leadership and Coach/raw/Podcasts/<Host> — <Episode Title>.md",
          raw_content="...",
          wiki_notes={"ConceptName.md": "..."},
          target_kb="Leadership and Coach",
          fast_sync=True,
          async_sync=True
      )
    • Clean temporary staging files via FastMCP clean_staging_temp().
    • Report progress and display modified notes with clickable Obsidian URIs to the user.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.