{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Skill Tree","title":"They're All Markdown Files","html":"","width":"100%","height":180,"duration":1748,"description":"In this trailer episode of The Skill Tree, Neil Roberts and Nick Nisi talk about why they started the show and the kinds of AI workflow conversations they want to have. The discussion centers on skills as reusable Markdown-backed instructions, transcript-first publishing, and the tools they keep returning to in day-to-day work.\nThe format is intentionally loose. There is no formal intro or outro, and the episode drops straight into a conversation about ideation workflows, spec generation, evaluation, and the mix of tools shaping how the hosts think about agent-assisted development.\nIn This Episode\n\nWhy The Skill Tree exists and what kinds of conversations the show is meant to explore\nHow Neil and Nick think about AI skills as practical workflow building blocks\nWhat makes a strong ideation and spec-generation workflow for agentic coding\nWhy transcripts, reference files, and structured Markdown can make audio content searchable and reusable\nEpisode Chapters\n\n00:00 Under the Skill Tree\n02:34 How Skills Clicked\n04:30 NebraskaJS and the Birth of Ideation\n15:40 DeepWiki as a Skill Generator\n19:01 Open Models, Cost, and Harnesses\n23:31 Guests, Segments, and the Show Format\n25:35 skilltree.fm, Podcast Metadata, and Skill Evals\nDiscussion Highlights\nStarting with a loose trailer episode\nNeil and Nick use this first episode to start publishing before every segment, workflow, and production habit is locked in. That makes the episode feel more like an initial conversation than a polished pilot, but it also gives a direct introduction to the show's focus: practical AI workflows, developer tooling, and how these systems hold up in real use.\nWhy skills matter even when they are \"just Markdown files\"\nOne of the recurring ideas in the episode is that the format is simple but the structure is useful. When instructions, references, and workflows are organized clearly, they become reliable inputs for both agents and humans. The conversation treats skills less like magic and more...","thumbnail_url":"https://img.transistorcdn.com/8gGwUeJyC9CnzImbdHEBVzHayyER5BSZCFNC734X0-U/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wYWMz/YTQyN2EyMzJiYzVl/NWU4OTg5YmFmZWRl/ZTA0ZC5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}