agentsclimarketplace

Uniloco story production

Skill Uniloco-Studios/uniloco-skills/skills/uniloco-story-production

Turn real experiences, raw material, travel memories, cultural material, or brand briefs into persistent Uniloco story-production projects with input-driven story intent, structure, script, bibles, shot lineage, provider-neutral generation planning with replaceable adapters, Mock generation, selective shot revision, versions, and production exports. Use when creating or continuing a multi-shot story project, inspecting why a shot exists, preserving character/location/object continuity, changing one shot without rebuilding the rest, or demonstrating the Uniloco CLI.From its SKILL.md

Install
npx -y skills add Uniloco-Studios/uniloco-skills --skill uniloco-story-production

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, 603 tokens by cl100k_base, as published. Nobody here has run it

Uniloco Story Production

Create and continue one project rather than treating generations as isolated clips. Keep creator decisions explicit and keep Provider execution replaceable.

Preflight

  1. Locate the repository root two levels above this Skill.
  2. Prefer the installed uniloco command.
  3. If it is unavailable, run:
PYTHONPATH="{baseDir}/../../src" python3 -m uniloco --help
  1. Never request an API key for Mock or dry-run modes.
  2. Read references/workflow.md before creating or revising a project.
  3. Read references/manifest.md when inspecting or editing lineage.
  4. Read references/providers.md before selecting a non-Mock Provider.

Workflow

Run the stages in order unless the existing manifest proves a stage is already complete:

init → develop → plan → generate → revise-shot → generate → export

Use:

uniloco init <input> --output <project>
uniloco develop <project>
uniloco plan <project> --provider mock
uniloco generate <project> --mode mock
uniloco revise-shot <project> SHOT-008 --instruction "<instruction>"
uniloco export <project>
uniloco validate <project>

Project rules

  • Treat manifest.json as the current project source of truth.
  • Preserve stable IDs for scenes, characters, locations, objects, references, and shots.
  • Require every shot to carry a script beat, narrative purpose, references, continuity contract, generation request, decision, version, and hash.
  • Record creator instructions verbatim in revision history.
  • Change only the requested shot and direct dependencies.
  • Verify unrelated shot hashes before reporting a selective revision complete.
  • Regenerate only plan items marked planned or revision_required.
  • Export the report and ZIP package only after project validation succeeds.

Provider rules

  • Use Mock for a complete offline demo.
  • Use dry-run to inspect the generic request intended for a cataloged Provider.
  • Treat --provider as an explicit user-selected Provider.
  • Use provider-neutral generation planning with replaceable adapters.
  • Do not claim or imply automatic Provider recommendation or routing.
  • Do not invent API endpoints, parameters, model names, jobs, or results.
  • Do not implement a real adapter without current official documentation, authorized credentials, explicit user intent, and adapter-specific tests.

Product language

Use only the public brand name “Uniloco”. Describe the product as human-led, model-enabled; experience-to-IP; project-based rather than clip-based; and story-first rather than prompt-first.

Do not claim a proprietary foundation video model, absolute consistency, or guaranteed distribution, monetization, or licensing outcomes.

What ships with it: 4 files

3.8 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.