<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on Vibe Coding</title><link>https://vibecoding.rest/category/productivity/</link><description>Recent content in Productivity on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/category/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>Slack</title><link>https://vibecoding.rest/mcp-servers/slack/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/slack/</guid><description>&lt;p&gt;The Slack server connects an agent to a workspace — listing channels, reading recent messages, searching history, and posting replies — using a bot token scoped to whatever permissions you grant it.&lt;/p&gt;</description></item><item><title>Google Drive</title><link>https://vibecoding.rest/mcp-servers/google-drive/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/google-drive/</guid><description>&lt;p&gt;The Google Drive server lets an agent search your Drive and read the contents of documents and spreadsheets, using OAuth scoped to your account.&lt;/p&gt;&#10;&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;&#10;&lt;p&gt;A lot of real work context — specs, meeting notes, planning docs — lives in Docs and Sheets, not in a codebase. This connector lets an agent reference that material directly instead of you manually copying content into a prompt.&lt;/p&gt;</description></item><item><title>Notion</title><link>https://vibecoding.rest/mcp-servers/notion/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/notion/</guid><description>&lt;p&gt;Notion MCP exposes a workspace&amp;rsquo;s pages, databases, and blocks to an agent through Notion&amp;rsquo;s API, so it can search, read, and edit content without a human copying text back and forth. It&amp;rsquo;s available both as a locally run npm package and a hosted remote endpoint.&lt;/p&gt;</description></item><item><title>Linear</title><link>https://vibecoding.rest/mcp-servers/linear/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/linear/</guid><description>&lt;p&gt;Linear MCP is Linear&amp;rsquo;s own hosted server, reachable at mcp.linear.app, that lets an agent create, update, and search issues, projects, and cycles in natural language instead of through the UI. It authenticates via OAuth on first connection rather than a static API token.&lt;/p&gt;</description></item><item><title>Loki Mode</title><link>https://vibecoding.rest/skills/loki-mode/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/loki-mode/</guid><description>&lt;p&gt;Loki Mode orchestrates dozens of coordinated AI agents to build, deploy, and operate a complete startup end-to-end, from a PRD through to a live, revenue-generating product.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Coordinating many agents toward one large goal needs explicit role division and hand-off structure, or the agents duplicate work or conflict. This skill packages that orchestration pattern rather than leaving it to be improvised per project.&lt;/p&gt;</description></item><item><title>Solo Skills</title><link>https://vibecoding.rest/skills/solo-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/solo-skills/</guid><description>&lt;p&gt;Solo Skills packages seven bilingual (English/Chinese) skills for solo founders and indie developers — launch tweets, customer emails, decision frameworks, and postmortems.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Solo founders repeat the same small set of communication and decision tasks — announcing a launch, writing a postmortem — often enough that having them as ready skills beats rewriting the format each time.&lt;/p&gt;</description></item><item><title>Google Workspace Skills</title><link>https://vibecoding.rest/skills/google-workspace-skills/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/google-workspace-skills/</guid><description>&lt;p&gt;This is a suite of Google Workspace integration skills covering Gmail, Calendar, Chat, Docs, Sheets, Slides, and Drive, with cross-platform OAuth handling.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Each Workspace API has its own auth flow and quirks; wiring up OAuth correctly per app is easy to get wrong. A packaged skill suite means that setup work is done once rather than per integration.&lt;/p&gt;</description></item><item><title>Notion Spec-to-Implementation Skill</title><link>https://vibecoding.rest/skills/notion-spec-to-implementation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/notion-spec-to-implementation/</guid><description>&lt;p&gt;This curated Codex skill turns a Notion spec document directly into an implementation plan and pull request.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Specs often live in Notion, separate from the codebase, which means implementation work starts with manually re-reading and re-typing the spec. A skill that reads Notion directly removes that translation step.&lt;/p&gt;</description></item></channel></rss>