A strong portfolio does not automatically make a strong pitch. Creative studios, photographers, and videographers may have years of compelling work, but finding the right evidence for one prospective customer takes time. I wanted to help creators answer a more useful question: Which work makes the strongest credible case for this customer, and why?

Creative Pitch Strategist starts with the prospect’s brief and an authorized NAS archive. It compares possible creative approaches, selects complementary evidence, and explains how that evidence supports the pitch. For example, residential interiors might demonstrate lighting expertise for a hotel proposal, while lifestyle photography suggests a direction for portraying the guest experience. The Skill can connect those strengths without inventing hotel clients or industry credentials.

The result is a personalized production package: a creative execution plan, an asset manifest, and a draft FCPXML timeline for timed pitches. The plan includes positioning, a storyboard of up to 20 seconds, timing, copy, and production direction. Strategy becomes a set of concrete creative decisions that an editor can carry forward.

I built the project as a Markdown-based Uliya Skill using UGREEN’s official creation kit. It coordinates the file, document, photo, and knowledge experts through documented capabilities. The parent workflow compares strategies and composes the package. Evidence gaps can trigger a targeted search refinement within the approved scope, with a maximum of two discovery passes. Because the media and project documents already live on the NAS, evidence can be searched in place.

The hardest challenge was making the workflow useful without allowing persuasive language to outrun the evidence. Inspection permission, reuse permission, and approval to write files are separate decisions. Excluded material stays excluded, empty searches remain empty, and uncertain reuse rights block client-facing export. I also learned to distinguish file creation, XML validity, media relinking, and successful editor import: each needs its own verification.

The current implementation includes the Skill instructions, production contracts, XML guidance, and validation tooling. Seven simulated reasoning walkthroughs were completed without NAS hardware, 32 local checks pass, and the package passes UGREEN’s static validation. Sample timelines pass Apple’s FCPXML schema. Live NAS execution, approval handling, model locality, media relinking, and editor import still need testing.

OpenAI Codex helped research documentation, author the Skill and tests, run local checks, and draft the submission materials. Claude helped with brainstorming and review. This Skill and its core workflow were newly developed during the hackathon.

Built With

  • codex
Share this project:

Updates

Submission history