Menu
Use when changing or operating Lucario's M2D failed-document replay, run-status, manual approval, or restart-from-beginning behavior.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Operating guide for the Oracle public-data ingestion agent: install and drive the elephant-xyz/skills (onboard-county + stage skills) against the oracle-node pipeline to discover, ingest, validate, refresh, and publish county property/permit plus Sunbiz/BBB data and coverage into Neon + Filebase/IPFS for MCP/Donphan/Miranda consumption. Covers the oracle-node checkout layout, sibling repos, AWS_PROFILE/AWS_REGION setup, the stage-skill map, and the coverage/IPNS handoff. Triggers on: oracle, onboard county, ingest county data, refresh Lee County, appraisal/permit/Sunbiz/BBB ingestion, oracle-node, county-discovery, coverage.
Operating guide for exploring Elephant data through the @elephant-xyz/mcp server in Cursor: Oracle open-data properties (appraisal, permits, Sunbiz, BBB), geo filters, lexicon schemas, and verified transform examples. Use when asking natural-language questions about Lee County properties, contractors, businesses, address mismatches, or schema fields — via MCP tools only. Not for Neon SQL (use-elephant-query-db) or county ingestion (use-oracle). Triggers on: elephant mcp, explore oracle data, donphan, contractors, BBB, Sunbiz, fort myers, address mismatch, nail salon, commercial property, property schema.
Extend the hypno Google Chat Asana initiative portfolio bot and WOW personal CLI workflows. Covers prompt-in-Markdown, gchat webhook flow, initiative project CRUD, acceptance-criteria parsing, portfolio analysis, my-tasks/story creation/store consolidation via manage-initiatives.mjs. Triggers on: hypno, asana initiatives, initiative portfolio, acceptance criteria, golden overlap, war plan initiatives, manage-initiatives, google chat asana bot, my tasks, WOW story, create-story, store-sync.
Use when changing or operating Lucario's M2D portfolio staging-config update flow, S3 config publication, GitHub PR creation, or approved sample-media verification.
Operating guide for the WOW Story Quality Agent (soofi-xyz/wow-website): when someone @-mentions the bot (Kirlia) in a comment on an Asana task of custom type Story, a Vercel runtime rewrites the story via LLM into the WOW format (clear title, Context / Description / Acceptance Criteria bullets / Demo Script), updates the task, and creates or refreshes a review subtask assigned to the mention author. Covers enabling/disabling projects via bot membership (discovery sweep), the org seed script and PATs, the webhook + 15-min sweeper trigger paths, the idempotent story_agent_tasks ledger, diagnosing missed or failed stories, and changing the WOW format prompt. Triggers on: story quality agent, story agent, WOW story format, rewrite Asana stories, mention the story bot, enable the story agent on a project, story agent missed a task, story_agent_tasks, seed-story-agent.
Use when implementing or changing the Persist service from its PRD: Neptune-backed graph persistence, Persist Blobs, GraphSON ingest, lexicon validation, deterministic IDs, Neptune CSV bulk load, Gremlin query APIs, and the lexicon-generated polymorphic GraphQL read surface with per-field resolution to Neptune, DynamoDB, or Interprose. Read reference/PRD.md first; combine with conkeldurr, machamp, and apply-engineering-guidelines.
| name | lucario-m2d-doc-replay |
| description | Use when changing or operating Lucario's M2D failed-document replay, run-status, manual approval, or restart-from-beginning behavior. |
Lucario can re-queue failed document-processing executions for an existing M2D runId by invoking the M2D run-tracker Lambda (replayFailedDocuments / getRunStatus) with the document-processing state machine ARN. This is document replay only for the replay_failed_documents action.
Full preprocessing rerun from the beginning uses Lucario's existing start_media_processing action with restartFromBeginning: true.
Use this skill when an operator or agent asks to:
You need a runId and a target environment label resolved from the user, user profile, task metadata, or runtime configuration.
Required fields:
action: replay_failed_documentsrunId: M2D run identifierenvironment: target environment labelOptional fields:
portfolioIdregionstackNameIf runId or environment is missing, ask once via an Asana comment or fail validation. Follow-up comments on the same task can supply missing fields when conversation memory applies.
Set per resolved environment, or use shared fallbacks:
lambda:InvokeFunctionRunTrackerFunction* and DocumentProcessingStateMachine* when explicit names/ARNs are omittedLucario's execution role needs lambda:InvokeFunction on run-tracker and cloudformation:DescribeStackResources on the M2D stack when using discovery. Cross-account replay may need an environment-specific assume role discovered from user profile, runtime config, stack outputs, or repo configuration.
replay_failed_documents does not require sourceBucket or sourceKey.replayFailedDocuments.getRunStatus with a bounded loop.Long-running runs may need a follow-up message or future EventBridge-based monitoring; a single Lambda invocation only covers bounded polling.
To restart preprocessing from the beginning, keep action: start_media_processing and set:
restartFromBeginning: truerunIdenvironmentapprovalTaskGidThat path reuses the existing run, forces skipStaging = true, forwards Asana gate task GIDs into M2D preprocessing, and automatically invokes M2D's manual approval callback after the restarted run reaches the approval wait state.