skills/perplexity-research/SKILL.md
AI-powered web research using the Perplexity API. Searches the live web and returns sourced answers with citations. Use when user wants to research, look up, search the web, or find current information.
npx skillsauth add RonanCodes/ronan-skills perplexity-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Search the live web via the Perplexity API. Returns sourced answers with citation URLs.
/perplexity-research "What are the latest changes in Claude Code?"
/perplexity-research "React Server Components best practices" --model sonar-pro
| Model | Best for |
|-------|----------|
| sonar | Quick facts, simple questions (default) |
| sonar-pro | Complex multi-step, more citations |
| sonar-reasoning-pro | Chain-of-thought, deep analysis |
Check these locations in order for PERPLEXITY_API_KEY:
${CLAUDE_PLUGIN_DATA}/.env (plugin-wide, survives updates — preferred)~/.config/ro/.env.envIf not found: direct user to https://perplexity.ai/settings/api to create a key (starts with pplx-), then save it to the plugin data dir: mkdir -p "$CLAUDE_PLUGIN_DATA" && echo "PERPLEXITY_API_KEY=pplx-..." >> "$CLAUDE_PLUGIN_DATA/.env". Or run /ro:setup-wizard --tokens.
# Load the key
PERPLEXITY_API_KEY=$(grep PERPLEXITY_API_KEY <env-file> | cut -d= -f2-)
# Make the request
RESPONSE=$(curl -s https://api.perplexity.ai/chat/completions \
-H "Authorization: Bearer $PERPLEXITY_API_KEY" \
-H "Content-Type: application/json" \
-d "{
\"model\": \"MODEL\",
\"messages\": [{\"role\": \"user\", \"content\": \"QUERY\"}]
}")
Default model is sonar. Override with --model flag or PERPLEXITY_MODEL from .env.
The response is OpenAI-compatible JSON. Answer: choices[0].message.content. Citations: citations array at root level.
Display as a Research Results heading with the answer text, then a Sources section with numbered citation URLs. Extract citations: echo "$RESPONSE" | python3 -c "import sys,json; [print(f'{i+1}. {u}') for i,u in enumerate(json.loads(sys.stdin.read()).get('citations',[]))]"
If the user wants to save, write to research-<slugified-query>.md with frontmatter (title, date, source: perplexity-api, model).
All /ro:* skills share one env file at ${CLAUDE_PLUGIN_DATA}/.env (Claude Code) or ~/.config/ro/.env (other agents). See .env.example at the plugin root.
PERPLEXITY_API_KEY=pplx-...
PERPLEXITY_MODEL=sonar
Never commit API keys.
development
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
devops
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
development
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
development
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h