PedroAVJ
UserAgentic SDK for prosumers
Categories
Indexed Skills (25)
oracle
Ask the user's logged-in ChatGPT Pro model, currently GPT-5.5 Pro, through Chrome using the Chrome plugin, wait for the answer, and bring the useful guidance back into the current Codex thread.
change-preview
Thin Symphony launcher for Pedro-facing standalone HTML change previews. It invokes Claude with its frontend-design skill, then the runner publishes the resulting HTML when that explicit review lane is requested.
review-handoff
Use when Pedro wants a Symphony human-review handoff artifact for a UI fix, especially a slower browser video that clearly shows the relevant behavior using existing auth/setup helpers instead of a full test-suite style demo.
coverage-pass
Compatibility mode for Symphony Requirements Elicitation. Use when Pedro asks whether stakeholder input, bugs, requirements, or meeting/chat follow-ups are covered in Linear/docs; report coverage gaps first and mutate Linear only when Pedro asks to fix coverage.
swe-stack-plugin-release
Release and upgrade SWE Stack plugins across both Codex and Claude Code. Use when changing a plugin in PedroAVJ/swe-stack, bumping plugin versions, publishing to the marketplace, or verifying that Codex and Claude installed caches both see the same plugin version.
android-phone
Inspect, test, debug, and control Android phones through ADB from Codex. Use when the user asks to inspect, screenshot, tap, swipe, type, or otherwise control their Android phone.
explainer
Produce a polished, standalone single-file HTML explainer for any topic the user wants explained — concepts, protocols, syntax, tools, decisions. Use Claude for aesthetic direction and visual-artifact judgment, and always support dark mode via prefers-color-scheme. Use when the user says 'make an html explaining X', 'explain X visually', 'make an explainer for Y', or asks for a visual/HTML write-up of a topic.
frontend-ui
Use when the user asks for app UI, frontend, visual, layout, interaction, customer-facing screen, dashboard, component, CSS, responsive, mobile, or browser-visible implementation work. Claude must own the UI implementation pass; Codex stewards, reviews, cleans up, verifies, and decides what ships.
gmail-cli
Use Gmail through the authenticated Google Workspace CLI. Use when the curated Gmail connector cannot expose raw message payloads, binary attachments, unsupported MIME types, original MIME source, or exact Gmail API metadata.
google-contacts
Resolve saved Google Contacts, phone numbers, organizations, and WhatsApp identities through the authenticated Google Workspace CLI.
google-drive-cli
Use Google Drive through the authenticated Google Workspace CLI. Use for Drive file search, metadata inspection, downloads, uploads, exports, folder creation, permissions, Meet recording files, and source-of-truth Drive artifacts when a CLI path is preferable to the curated connector.
google-tasks
Manage Google Tasks through the authenticated Google Workspace CLI. Use for task list discovery, task reads, task creation, updates, completion, reopening, deletion, movement, and Google Tasks API limitation questions.
azure-merge
Run the Azure DevOps Symphony merge lane: publish or reuse an Azure DevOps PR, merge it, babysit relevant rollout proof, verify live behavior when scoped, and reconcile the tracker after proof is satisfied.
azure-publish-changes
Publish local changes for an Azure DevOps-hosted Symphony lane: confirm scope, stage intended files, commit, push, and create or update an Azure DevOps pull request.
codex-review
Run Codex code review as a Symphony closeout check: local dirty changes, PR branch vs main, parallel tests, and accepted-finding cleanup.
evidence-intake
Preserve meeting, call, audio-note, transcript, Drive, Gmail, or local media evidence before Symphony issue intake, coverage passes, review artifacts, or Linear extraction. Do not create Linear issues by default.
implementation-dispatch
Use when Pedro has approved a Linear work packet and wants Symphony to create a fresh Codex thread/agent to implement it. This skill takes the approved Linear issue plus source pointers, creates a separate implementation thread, sends a bounded prompt, and reports the new thread back without implementing in the current thread.
merge
Run the explicit Symphony publish/merge/release-proof lifecycle: branch, PR, merge, rollout babysitting, tracker reconciliation, and worktree cleanup across GitHub, Azure DevOps, or another repo host.
requirements-elicitation
Use when Pedro wants Symphony to turn messy stakeholder input, WhatsApp messages, meeting/email evidence, screenshots, docs, or repo context into an agreed Linear work packet before implementation. This skill talks through meaning and scope first, creates/updates Linear only after approval, and does not write product code.
sprint-review
Use when Pedro explicitly asks for a Symphony sprint review, demo agenda, stakeholder-facing HTML review, or grounded presentation artifact.
symphony
Use only when Pedro explicitly asks for Symphony or a Symphony-owned meta-workflow: requirements elicitation, implementation dispatch to a fresh thread, evidence intake, source-of-truth audits, Linear lifecycle hygiene, Codex review, merge/release proof, review artifacts, status summaries, or notifications after agent work completes.
Read WhatsApp chats, contacts, message context, and message media; create reviewable local drafts; and send only explicitly approved WhatsApp messages.
elevenlabs
Use ElevenLabs audio and speech tooling. Documented use cases include Scribe transcription, diarization, language hints, and keyterm biasing.
linear-issue-writer
Internal/compatibility rules for writing grounded Linear issues from Symphony Requirements Elicitation. Use when Pedro explicitly asks to write/rewrite a Linear issue body, or when another Symphony skill needs concise issue-body policy.
issue-intake
Compatibility alias for Symphony Requirements Elicitation. Use when Pedro asks for a Symphony issue-intake pass over WhatsApp/meeting/email evidence to decide do-now Linear work; follow requirements-elicitation as the canonical workflow.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.