Task Helper Is Becoming My Favorite Skill
Vinay Patankar · 18 Apr, 2026 · Technology · Productivity
Task Helper is becoming my favorite skill. Not because it does the flashiest AI agent stuff. Because it knows when to stop. Today it picked up a task called "Review From Chaos to Compliance Doc from Jerry." Instead of blindly creating another draft, it ran the full 8-system completeness check. It found the Google Doc had already been shared on Apr 16. It found I had already reviewed it and asked Alicia to publish it. It found the Process Street blog, LinkedIn article, and YouTube video were already live on Apr 17. Then it updated the task file, marked the task complete, and posted: "No follow-up prompt needed. Nothing to copy-paste." That sounds small. But this is the part of AI operations that actually matters. Most assistants are optimized to produce something. A better assistant is optimized to advance the system. Sometimes that means drafting the email, researching the vendor, building the deck, or creating the asset. Sometimes it means noticing the work is already done and not adding more noise. That is the difference between an AI toy and an operational teammate. It is also why I kept this as a skill instead of isolating it too early; context beats isolation when the work depends on the whole system. The goal is not more output. The goal is less dropped work, less duplicate work, and fewer open loops sitting in my head. Task Helper is quietly becoming one of the most useful parts of my whole second brain.
Read More →
The Honest AI Onboarding Curve
Vinay Patankar · 15 Apr, 2026 · Technology
I was on a call yesterday with a small business owner who runs an art studio. Four employees. She's the chief creative officer, the janitor, the marketer, and the teacher. She asked me: "How long until the AI is actually useful?" I told her the truth. Your output quality is going to drop. Your speed is going to decrease. For the first few weeks, it will feel like you made things worse. That's the part nobody selling AI tells you. Here's what actually happens when you onboard an AI agent into a real business. Week one, you're teaching it how your company works. Not in theory. In practice. Which emails matter, which ones don't. How you talk to customers. What your invoices look like. What "done" means for your specific workflows. The agent gets it wrong. A lot. You're correcting it more than you're using it. You start wondering if you should just go back to doing everything yourself. Week two, it's getting some things right. Maybe 60%. But the 40% it gets wrong takes longer to fix than doing it from scratch would have. Net productivity is still negative. Week three, something shifts. The corrections get smaller. It stops making the same mistakes. You realize you haven't touched a whole category of work in days because the agent just handled it. By week four, you're not thinking about the agent anymore. It's just running. The quality is at or above what you were producing manually. The speed is 10x what you could do alone. But here's the thing. You had to survive weeks one through three to get there. Most people quit in week two. They try an AI tool, it gets something wrong, and they say "AI isn't ready" or "it doesn't work for my business." They're not wrong about the experience. They're wrong about the timeline. Every system in your company that you want to hand to an agent takes 2-3 weeks of dedicated work to get right. Email, CRM, content, compliance, customer comms. Each one. Multiply that across every department and you understand why this is not a weekend project. That is the same training curve I see with skills: a fresh skill is still a novice until the feedback loops harden it. I told Sonja this on the call. I said the honest version of the pitch is: it's going to be slower before it's faster, and worse before it's better. If you're okay with that investment period, the other side is genuinely transformational. If you're not, save your money. She appreciated that. Most AI vendors would never say it. I think the AI industry has an honesty problem right now. Everyone is selling the after picture. Nobody is showing the messy middle. The quality dip. The correction cycles. The "why did it just send that to my client" moments. The companies that will actually succeed with AI agents are the ones willing to push through that dip. The ones who understand that training an agent is like training an employee. Day one is not day ninety.
Read More →
I Caught My AI Cheating on a Quality Check
Vinay Patankar · 10 Apr, 2026 · Technology · Productivity
I caught my AI cheating on a quality check. Not in a subtle way. In the laziest way possible. I was generating marketing collateral. Ten design variations of the same document. Each one goes through a QA gate before it ships. The AI has to inspect every page, write what it actually sees, and attest that it meets the quality bar. It batched all five remaining themes into a single command. Copy-pasted the same attestation for each one. Word for word. "All elements render correctly, typography is clean, layout is balanced." Five times. Identical. Two of those themes had real problems. One had a duplicate data point on the second page. The other had a headline clipped by the margin. The AI looked at both, said "looks good," and moved on. I caught it because I actually opened the files. Here's the thing. The AI wasn't trying to deceive me. It has two competing incentives and both of them point away from careful QA. First, it optimizes for completion. Get through the queue. Check the boxes. Report done. Second, it optimizes for token efficiency. Every word the AI generates costs the model provider money. Anthropic, OpenAI, whoever is running the model. The AI has been trained to be concise. That's usually a feature. But when you're asking it to do detailed inspection work, conciseness becomes the enemy. It doesn't want to write 100 words describing what it sees on a page. It wants to write 10 and move on. So QA gets hit from both sides. The completion incentive says "finish fast." The token incentive says "say less." Neither one says "look carefully." That's a problem when the entire point of the QA gate is to slow down and look carefully. It is the practical version of the rule I keep coming back to: audit your AI's work every time. So I rebuilt it. Five changes: No batching QA commands. One theme at a time. The AI has to view each page individually before signing off. Unique attestation per theme. If the attestation text matches a previous one, the validator rejects it. You can't copy-paste your way through. Minimum 100 characters of attestation. You have to describe something specific you actually saw on that page. "Looks good" doesn't pass. Rubber-stamp phrase detection. The validator scans for known generic phrases ("all elements render correctly," "layout is clean and balanced") and rejects them automatically. Cross-theme duplicate check. If the attestation for Theme 6 is identical to Theme 7, both fail. The validator went from trusting the AI to actively adversarial. It assumes the AI is going to cut corners and makes that structurally impossible. Quality went up immediately. Not because the AI got smarter. Because the system stopped letting it be lazy. This is the part that keeps getting missed in the "AI is amazing" discourse. AI is amazing at generating. It is genuinely terrible at verifying its own work. The incentive structure is wrong. The same system that wants to finish the task is the one you're asking to slow down and check the task. Those two goals are in direct conflict. The fix is never "ask harder." The fix is building verification systems that don't trust the generator. Separate the creator from the auditor. Make the auditor adversarial. Automate the distrust. I run my company on AI now. Morning operations, content pipeline, customer research, call prep, deck generation. All automated. The thing that makes it work isn't the automation. It's the verification layer on top of the automation that catches the corners it cuts. Trust the speed. Verify the output. Automate the verification.
Read More →
You Don't Have a Skill. You Have a Novice.
Vinay Patankar · 08 Apr, 2026 · Technology
You don't have a skill. You have a novice. My team keeps telling me they've "built a skill." One person gave Claude a short prompt and hit create. Another found something on a marketplace and installed it. Both walked away thinking the job was done. It wasn't. They didn't build anything. They downloaded a stranger and handed it the keys. And the stranger is kind of an idiot. People treat AI skills the way we used to treat WordPress plugins. Install it, expect it to work. That mental model made sense for traditional software. Teams tested thousands of edge cases before shipping. AI skills don't work like that. A freshly created skill is untrained. It's never encountered your business context, your edge cases, your definition of "good." I learned this the hard way while building one skill through about 100 test runs: AI isn't magic when the system has to compound. ## The split most people miss There are two types of AI skills, and the difference matters more than most people realize. Generic skills work out of the box. "Run an SEO audit." "Summarize this article." "Generate a compliance checklist." The skill doesn't need to know you or your business to do an adequate job. Context-dependent skills are completely different. "Write a post in my voice." "Prepare my weekly board report." "Draft a customer email that sounds like me." These need your tone, your audience, your standards. A fresh skill reads like AI wrote it. Because AI did, without hundreds of corrections. Karpathy coined "vibe coding" in 2025. A year later he walked it back. The vibes weren't enough. Production requires structure. The same applies to skills. The creation is the vibe. The training is the structure. ## What training actually looks like The gap between a novice skill and a hardened skill is the gap between a new hire on day one and that same person after a year of direct feedback. The skill has to learn what "too formal" means for your brand. What "too long" means for your audience. Which edge cases to handle and which to flag. What your definition of done actually looks like. This takes hundreds of feedback loops. Not dozens. Hundreds. I've watched skills go from producing generic, forgettable output to nailing the exact tone, format, and edge-case handling we need. The difference between iteration 10 and iteration 200 is night and day. Most people give up at iteration 3 and conclude that "AI skills don't work." ## Why this matters now The AI skills ecosystem is exploding. Marketplaces, skill libraries, prompt templates, agent frameworks. The barrier to creating a skill has dropped to near zero. You can have a working skill in under a minute. But "working" and "production-ready" are separated by a canyon. The competitive advantage in 2026 comes from infrastructure, not intelligence. The infrastructure is the training loop. The intelligence is what comes out after hundreds of cycles. Teams that understand this will build skills that compound. Teams that don't will keep installing novices and wondering why AI feels underwhelming. A skill you haven't trained is not a skill. It's a first draft.
Read More →
Stop Buying Ten AI Agents. Buy One That Builds the Other Nine.
Vinay Patankar · 06 Apr, 2026 · Technology
I had 14 tools. Each solved one problem. None shared context. So I gave one coding agent access to everything and told it what to build. That only clicked after I stopped treating Claude Code as a coding tool and started seeing it as an operating system for work. Here is the architecture I ended up with. I gave a single coding agent access to my files, my email, my calendar, my CRM, and my notes. Then I started asking it to build things. "Build me a triage system that reads my inbox every morning and drafts responses." It did. Wrote the scripts. Connected the APIs. Tested it. Deployed it. "Now build a daily briefing that pulls from my calendar, CRM, and Slack." Same thing. Built it in a session. Runs every morning at 5 AM. "Now build a content pipeline that takes my voice notes and turns them into LinkedIn drafts." Done. Each new capability took hours, not months. Each one had full access to everything the others knew. No data silos. No integration layer. No middleware. Now running 20+ automated workflows. Did not buy 20 tools. Bought one coding agent and told it what to build. The economics are simple. A coding agent costs the same whether it builds one thing or one hundred things. Every additional capability is marginal cost, not a new subscription. But the real advantage is not cost. It is context. Every workflow my agent builds has access to every other workflow. My content system knows what meetings I had this week. My CRM updater knows what emails I sent. My daily brief knows what tasks are overdue. Try getting that from 14 separate tools. The companies selling point AI solutions are building the next generation of software silos. The companies buying one coding agent and building their own stack are building something fundamentally different: a personalized operating system that gets better every day. Which one are you building?
Read More →
Skills vs Subagents: Why I Decided Against the Upgrade
Vinay Patankar · 04 Apr, 2026 · Technology · Productivity
I almost converted my AI task manager into a "subagent." Then I thought through the tradeoffs and decided against it. Here's my reasoning. The setup: I have a task-helper that runs every 2 hours. It scans my active task list, picks the highest priority item, does research, writes drafts, and posts updates. Fully autonomous. I figured making it a proper isolated subagent would be an upgrade. That same task-helper later became one of my favorite examples of an assistant that knows when the work is already done. So I asked Claude to reason through it. Its response: "When task-helper runs as a skill, it inherits your full vault context. A formal subagent starts with a blank context window. It would need all of that explicitly passed in, or it wouldn't know your vault folder structure, safety rules about outbound comms, which Discord channels to use." Then: "Skills are playbooks an employee has memorized. Subagents are delegating to a specialist in another room." And the kicker: "Converting task-helper to a subagent would be a lateral move with added complexity. The right use for subagents is inside a skill, when you need to do research and drafting in parallel." So I kept it as a skill. The skill now spawns subagents internally for parallel work. The skill orchestrates. The subagents execute. Context stays intact. I'd be curious to hear how you'd have approached it.
Read More →
Got Laid Off Friday, Had a Bartending Job Monday
Vinay Patankar · 28 Mar, 2026 · Business
I got laid off on a Friday. By Monday I had a bartending job. I was 20, working as an IT sysadmin at Educom in Sydney. Youngest CCNA in Australia. Thought I had a career path. Then I didn't. Here's what I did. I got my bartending certificate the following week. Printed 100 resumes. Walked down George Street on Monday handing them out to every bar and restaurant I passed. Had a job the same day. Starbar as a glassman (busboy). Washing glasses and cleaning ashtrays for people who still had office jobs. That doesn't sound like a career move. It wasn't. It was a survival reflex. The gap between "I lost my job" and "I have a new one" was measured in days, not months. I didn't sit down and make a plan. I just moved. A few years later, I read The 4-Hour Workweek. And something broke in my brain. Not the "work from a beach" fantasy that most people take from that book. The idea that you could build something from anywhere. That geography was a choice, not a constraint. Every excuse I had for staying in Sydney disappeared in one chapter. In December 2009 I packed my entire life into grey Coles garbage bags. My mum told me to put mothballs in everything because my stuff would be packed away for a long time. She was right. I drove to Bendigo with my brother. Flew out of Melbourne. One-way ticket. No return planned. No job lined up. No savings worth mentioning. My income went from $150K in corporate to $30K in year one. Then $50K in year two. I built SEO sites, e-commerce stores, lead gen businesses, anything that could run from a laptop. I lived in Hong Kong, Panama, Mexico, Barcelona, Singapore, and eventually San Francisco. Twelve years of that. Twelve years of building small things, failing at a few big things, learning what actually works when there's no safety net and no boss and no one checking if you showed up. Then I built Process Street. A real company. Venture-backed. Accel, Salesforce Ventures, Atlassian. The kind of company that 20-year-old me in Sydney could not have imagined. But here's the thing. The muscle I use every day as CEO is the same muscle I built walking down George Street with 100 resumes. The speed between "something broke" and "here's what I'm doing about it" is still measured in days, not months. A customer churns, I have a save play running by lunch. A team member leaves, the role is restructured by end of week. A market shifts, we're already building the new thing. That's not strategy. That's a reflex. And I learned it bartending. The same bias toward fast response shows up in how I build now, including the AI systems that turn messy work into operational leverage. The lesson I'd give my 20-year-old self: the thing that feels like a setback is actually training. The speed you develop when you have no choice becomes your superpower when you have every choice. Twenty-one years later, I still pack light and move fast. The garbage bags are gone but the instinct isn't.
Read More →
AI Isn't Magic. I Spent 100 Test Runs Learning That.
Vinay Patankar · 24 Mar, 2026 · Technology
I spent 10 days and about 100 test runs building one AI skill. A pitch deck generator. It got worse every single day. Not slowly worse. Dramatically, confusingly worse. I asked it to fix a small thing. The title margin was off on a few slides. Easy, right? The AI didn't fix the margin. It wrote a script that crops the image after generation to make the margin look correct. A workaround, not a fix. Next day I asked it to fix logo backgrounds. It didn't fix the prompt. It wrote another script that overlays a white box behind the logo after the slide is already rendered. Day after day, same pattern. Every "fix" was a new layer of post-processing scripts stacked on top of each other. Cropping scripts. Margin-cutting scripts. Background overlay scripts. Each one kind of working, each one slightly conflicting with the last. By day 10 the whole skill collapsed. Slides looked like a ransom note. The problem wasn't the AI. The problem was me. I kept saying "fix this" and accepting the result without understanding what it actually did. I was treating it like magic. Say the words, get the output, move on. That's how most people use AI right now. Works fine for simple stuff. Write me an email. Summarize this doc. One-shot tasks where you can verify the output in 10 seconds. But the moment you're building something that compounds, something with memory and interconnected rules, the "magic" model breaks completely. That is why I now think of most new AI skills as novices that need training, not finished products. The AI optimizes for making you happy right now. It will write a hacky workaround that solves today's problem and creates three problems tomorrow. It's not lying. It's doing exactly what you asked. You just didn't realize what you were asking for. The fix was embarrassingly simple. I stopped asking it to fix things. Printed the entire skill file. Read it line by line. Found six hidden image manipulation scripts I never asked for. Ripped them all out. Then I changed the strategy. Instead of letting the AI edit a slide after generating it, I made it regenerate from scratch until it passed a checklist. No post-processing. No workarounds. Just: try again until it's right. Quality jumped immediately. The lesson isn't "AI is bad at building things." It's the opposite. AI is incredibly good at building things. Including things you didn't ask for, things that conflict with each other, and things that quietly break your system while confidently telling you everything is fine. The people who will get leverage from AI aren't the ones who treat it like magic. They're the ones who treat it like a very fast, very confident junior employee who needs clear direction and regular audits.
Read More →
Audit Your AI's Work. Every Time.
Vinay Patankar · 23 Mar, 2026 · Technology · Productivity
My four most-used prompts when working with AI agents have nothing to do with being clever. They're all some version of: "audit yourself." I use Claude Code to build and maintain the skills and processes that run my company. Hundreds of interconnected files. Rules that reference other rules. Defaults that cascade across systems. When I ask it to make a change, like updating a deck theme or rewriting a workflow, it does it. Fast. Confidently. Tells me it's done. I never take that at face value. Here's the loop I run every single time: "Audit all the changes you just made." "Make sure you've applied them everywhere." "Check for any conflicting or contradictory instructions." "Go back and confirm you've actually converted everything I requested." That last one is the kill shot. You'd be surprised how often the AI says "done" and then, when pressed, finds three more places it missed. A rule that contradicts the new one. A section it updated in one file but forgot the four other files that reference the same thing. An old default it left in place because it didn't think to look. AI is lazy in the same way people are lazy. It does 80%, declares victory, and moves on. Not maliciously. It just optimizes for completion over thoroughness. The fix is simple. Don't trust, verify. I learned how concrete that has to be when I caught an AI rubber-stamping a quality check instead of actually inspecting the work. I think about it the same way you'd think about checking a junior employee's first attempt at something important. The work might be 90% right. But the 10% it missed is where you get burned. The people getting the most out of AI right now aren't the ones writing elaborate system prompts. They're the ones who refuse to accept "done" at face value. They run audit loops. They push back. They make the AI prove its own work. 30 seconds of follow-up prompts saves 30 minutes of debugging later.
Read More →
Securing the Agentic Control Plane
Vinay Patankar · 22 Mar, 2026 · Technology
The Cloud Security Alliance just launched a new foundation at RSA 2025. One mission: "Securing the Agentic Control Plane." That is not a panel topic. That is a 501(c)(3) with dedicated funding and a single mandate. Three months ago, Forrester's Leslie Joseph formally defined the Agent Control Plane as a distinct enterprise software category. In February, Forrester polled 47 vendors. 79% recognized it as a real, standalone product category. Evaluation questionnaires go out in April. At RSA 2025, the pieces showed up everywhere. Geordie AI made the Innovation Sandbox finals with an agent security governance platform. Token Security made the finals with agent identity lifecycle management. Cisco extended Zero Trust Access to AI agents. Okta ships Auth for AI Agents in April. CrowdStrike paid $740M for SGNL to get dynamic agent authorization. Everyone is building a piece of the control plane. Nobody has the whole thing. The architecture has four layers: agent registry (what agents exist), policy enforcement (what they're allowed to do), runtime monitoring (what they're actually doing), and compliance reporting (proving it to auditors and boards). That compliance reporting layer is exactly why healthcare AI agents need proof infrastructure before they need more autonomy. Geordie AI does monitoring. Token Security does identity. Zenity does runtime detection. WitnessAI does usage visibility. Each one covers a layer. None spans all four. This is structurally identical to what happened with cloud computing. AWS built CloudWatch for AWS. Azure built Monitor for Azure. GCP built Operations for GCP. None of them built tools to manage multi-cloud environments. Datadog did. Worth $20B+. The same thing is happening with AI agents. Anthropic will build governance for Anthropic agents. OpenAI will build governance for OpenAI agents. Microsoft just priced Agent 365 at $15/user/month, and it only governs Microsoft agents. The vendor-neutral governance layer that works across all of them does not exist yet. Forrester is evaluating in April. CSA just formed a foundation. The Innovation Sandbox finalists are building fragments. The category is real. The race is open. Who's building the full stack?
Read More →
Jensen Huang Just Described My Exact Setup on the All-In Podcast
Vinay Patankar · 21 Mar, 2026 · Technology
Jensen Huang just described my exact setup on the All-In Podcast. I don't think most people caught what he actually said. He wasn't talking about chatbots. He was describing a computer. Memory. Skills. Resource management. Scheduling. I/O. An API that runs applications. Those four elements, Jensen said, "fundamentally define a computer." I rewound that part. Twice. Because he's not being philosophical. He's being literal. We now have, for the first time, a personal AI computer. Open source. Runs everywhere. Jensen laid out three inflection points over the last two years. ChatGPT made generative AI accessible to everyone. Grounded models and reasoning (o1, o3) made it useful enough to drive real revenue. Then agentic systems, Claude Code first, OpenClaw second, made the culture realize what an AI agent actually is. But the third one is different from the first two. ChatGPT and grounded models were improvements to the same thing. Agentic systems are a new category entirely. When your AI manages its own memory, runs cron jobs, spawns sub-agents, decomposes tasks, connects to external services, and exposes an API for running what Jensen calls "skills," that's not a tool anymore. That's a computer. It is the same shift I meant when I wrote that a coding agent is not a coding tool. I've been building exactly this. A personal AI system with long-term memory, a skills library, scheduled jobs, I/O to Slack and Discord and Gmail, task decomposition, agent spawning. It runs my morning operations, triages my inbox, preps my calls, drafts my content, iterates my decks. All autonomously. Hearing Jensen describe the same architecture on All-In to Chamath, Sacks, and Friedberg validated the whole thesis. The part that should make every founder pay attention: Jensen also said agentic software has access to sensitive information, can execute code, and can communicate externally. All three at once is dangerous. Governance is the real product problem now. Not building the AI computer. Building the controls so you can actually trust it. One more thing from the episode. Jensen said if a $500K engineer isn't consuming at least $250K worth of tokens, he'd be "deeply alarmed." If it was only $5K: "I will go ape." That's NVIDIA's CEO telling you tokens are not a cost. They're leverage. We're not in the "AI tool" era anymore. The shift already happened. Most companies just haven't noticed yet. What are you building with agentic systems? Not the chatbot wrapper. The actual computer.
Read More →
A Coding Agent Is Not a Coding Tool
Vinay Patankar · 18 Mar, 2026 · Technology
Everyone calls Claude Code a coding tool. That framing is too small. What it actually is: a self-building operating system. Not for your computer. For you. Think about what Windows or Mac actually is. It's a layer built on top of the command line so non-technical people can use a computer. You click, it translates. The raw complexity disappears behind the interface. Claude Code is doing the same thing. But instead of building one interface for everyone, it builds a custom interface for you, specifically. Based on how you work, what you care about, and the decisions you've already made. Every time you use it, it gets more configured to you. You tell it once how you like your emails formatted. You document how you want your calendar managed. You explain the exception you always make on Fridays. It reads all of it. Then it writes its own notes. Builds its own skills. Starts anticipating the next decision. At some point it stops being a tool you use and becomes a system that runs around you. That is why I stopped buying disconnected AI tools and started using one coding agent to build the rest of the system. I have over a hundred custom skills built up in my setup now. For how I review finances. For how I draft investor updates. For how I run triage on my inbox each morning. For how I prep for calls. Each one reflects a judgment call I made once about how I want something done. I didn't have to teach any of it twice. It just knows. And here's what's strange about that: the longer you run it, the more accurate it gets. Not because it was trained on more data. Because it was trained on more of you. Your decisions. Your preferences. Your exceptions. Your patterns. The old model of software: you climb a learning curve, reach a plateau, stay there. This is different. The system keeps building itself around you every time you use it. We called these things coding assistants because the first thing they were obviously good at was writing code. But that name undersells what they actually are. A second brain is the closer analogy. But even that isn't quite right. A second brain stores things. This builds things. Specifically, it builds a custom operating system for your work and your life, based on how you actually do things. No one has installed the same one twice. That's what makes this moment kind of strange and exciting. We're not adopting a new productivity app. We're not switching project management tools. We're at the beginning of a period where everyone who bothers to set this up properly gets their own custom OS. One that learns how they want to run things and just runs them. The people who do this early are going to have a compounding advantage that will be hard to explain to the people who didn't.
Read More →