القائمة
Use when the user says /todo, asks to update the shared todo list, or wants any project to track current work in Riley's shared todo document.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Find paid promotion, sponsorship, brand deal, influencer campaign, creator partnership, affiliate, and paid collaboration opportunities in Riley's Gmail or email exports; research each brand/client; dedupe follow-ups; prioritize fit; and produce a Markdown table, document, or spreadsheet of brand leads with notes. Use when the user asks to scan recent email for brand deals, paid promo offers, sponsorship pitches, creator partnerships, or to turn those leads into a table/spreadsheet/doc.
Use Buffer's GraphQL API to inspect Buffer accounts, organizations, channels, queues, posts, daily limits, and to create Buffer Ideas, drafts, scheduled posts, queued posts, or media posts. Use when the user asks to draft, schedule, queue, publish, edit, delete, review, list, or manage social posts through Buffer, or asks what is connected in their Buffer account.
Build, sign, and install iOS apps on real devices using the Vibecode signing service. Use when the user wants to build an iOS app from source, sign an iOS app, install on their iPhone, register a device, set up Apple Developer auth, or work with the iOS build/sign/distribute pipeline. Also triggers for "test on device", "put this on my phone", "ship it to my iPhone", or any request to get a Swift/iOS app running on a real device.
Create polished Excalidraw diagrams from text descriptions. Use when the user asks for a diagram, flowchart, architecture diagram, decision tree, process flow, data flow, system overview, or similar visual explanation, or says "draw this", "diagram this", "visualize this", or "make a chart". Produces styled `.excalidraw` files with consistent colors and can export a shareable excalidraw.com URL.
Use when working with Firebase from the terminal: repairing or installing the Firebase CLI, authenticating, selecting projects, creating or managing Cloud Firestore databases, creating or querying Realtime Database instances, registering Firebase apps, or printing SDK config. Prefer this skill when the user asks to add Firebase to an app, create a Firebase database, inspect Firebase project resources, or run Firebase CLI commands safely.
Use when Codex needs to find images on the public internet and save them into a local directory, especially for brand assets, moodboards, research boards, reference pulls, or site-specific image collection. Supports SerpAPI Google Images search for query-driven discovery and Firecrawl scrape/map workflows for extracting images from specific pages or whole sites.
| name | todo |
| description | Use when the user says /todo, asks to update the shared todo list, or wants any project to track current work in Riley's shared todo document. |
Point todo updates to this document:
/Users/rileybrown/Documents/Codex/2026-05-09/please-make-a-markdown-file-that/Todo list.md
Use the emoji itself as the bullet:
When updating the document, keep it simple. Do not add a status key, markdown bullets, checkboxes, or [x] marks. Add current project tasks under Not done, use 🔵 for video ideas too, move completed work to Done, and put do-later items in Backlog.
When adding or updating a todo item from an active Codex chat thread, append a clickable thread backlink at the end of that item's line.
Direct codex://threads/<thread-id> links are not reliably clickable in Markdown. Use a normal local web link labeled View Thread that redirects into the Codex deeplink:
[View Thread](http://127.0.0.1:8796/<thread-id>/)
Use the active thread's real thread ID in the URL only. Do not print or append the raw thread ID anywhere in the visible todo text. If the thread ID is not available in the chat context, ask Riley to paste the copied Codex deeplink and extract the ID from codex://threads/<thread-id>. Do not invent a thread ID.
For each thread link, create or update this redirect page:
/Users/rileybrown/Documents/Codex/2026-05-09/please-make-a-markdown-file-that/thread-link-server/<thread-id>/index.html
The redirect page should immediately send the browser to codex://threads/<thread-id> and include a fallback button labeled View Thread. Do not display the raw thread ID or the raw codex://threads/<thread-id> URL on the page.
If the local thread-link server is not already running, serve the thread-link-server folder on 127.0.0.1:8796. Prefer the existing LaunchAgent if present:
/Users/rileybrown/Library/LaunchAgents/com.riley.codex-newsletter-thread-link.plist
When the todo item is about a document or artifact, include the artifact link inline before View Thread. This includes Google Docs, Google Drive folders/files, Notion pages, local HTML previews, GitHub PRs/issues, Vercel deployments, or any other source/output link created or used for the task. Do not leave the user hunting for the document later.