Perplexity Computer Skills - Extend Computer’s capabilities with repeatable instructions
by•
Every builder has SKILL.md files sitting in their Claude Code or Codex setup.
Perplexity Computer Skills lets you import them directly, no rewriting, no translating.
Your workflows activate automatically based on context.
Same skills, 19-model execution.
Replies
This solves a real pain point. Love seeing workflow portability across AI tools.
Love the portability angle here - having consistent workflow definitions across different AI tools is a big productivity win. The 19-model support is impressive. How do you handle version conflicts when skill files get updated?
Congrats on the launch! As a heavy user of Gemini, Claude Opus, and Manus, reading through this immediately gave me strong Manus vibes—and I mean that in the best way possible.
Moving from "answering questions" to "executing multi-step workflows" is exactly what makes agentic tools like Manus so powerful. Seeing Perplexity adopt this "Computer" orchestration approach, especially with SKILL.md portability, is a massiveee step forward.
I'm just worried about the costs a bit. Subscription-based is great, as it allows us power users to outpace standard API costs. But since this routes tasks through various sub-models under the hood, I wonder if it might end up being as pricy or even pricier than Manus. I have my largest non-api costs there right now.
Looking forward to tryint it out. Really exciting
Having portable workflow formats across different AI coding tools is exactly what the developer ecosystem needed. The context-aware triggering approach is clever - letting the tool infer intent rather than requiring explicit commands reduces friction significantly. Excited to test how this works with complex multi-step automations.
The portable workflow concept here is brilliant - having skills that understand context and fire automatically rather than needing explicit invocation is a game-changer for builder productivity. Curious how the 19-model routing works - is it deterministic based on skill type or more dynamic? Also interested in how team collaboration on shared skill libraries would work.
MacQuit
The SKILL.md portability angle is what makes this genuinely interesting. We're seeing the same pattern across the ecosystem — Claude Code, Codex, and now Perplexity all converging on markdown-based skill definitions. It's like Dockerfiles for AI workflows.
What I find exciting is the 19-model execution part. Right now most of us are locked into one model per skill. Being able to run the same workflow across different models means you can actually benchmark which model handles your specific task best — not just generic benchmarks, but YOUR actual workflow.
For context, I build native macOS apps and use Claude Code with custom skills daily. The pain point has always been: if I invest time crafting a perfect workflow in one tool, I'm locked in. Making skills portable changes the economics of investing in workflow engineering.
Curious: does it handle skills that rely on tool-specific features like Claude Code hooks or MCP servers? That's where portability usually breaks down.