Extract shared Runway context and reduce skill repetition#9
Open
robinandeer wants to merge 1 commit intomainfrom
Open
Extract shared Runway context and reduce skill repetition#9robinandeer wants to merge 1 commit intomainfrom
robinandeer wants to merge 1 commit intomainfrom
Conversation
Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Durable Runway API rules — auth, output URL expiry, task polling, credits, moderation — are repeated across many skill docs. Updating one fact (e.g. API version) means touching multiple files and hoping none get missed.
Currently duplicated across skills:
RUNWAYML_API_SECRET: 12 skillswaitForTaskOutput(): 7 skillsSolution
Add
runway.mdas a single shared context document for cross-cutting platform rules. Trim the most repetitive sections fromrecipe-full-setup,integrate-video,integrate-image, andintegrate-audioto reference the shared doc instead. Also point the README's API Reference section torunway.md.Borrowed from vercel/vercel-plugin which uses a repo-wide context document (
vercel.md) to capture durable ecosystem guidance once, rather than restating it in every skill.How to test
runway.mdfor accuracy and completenessintegrate-video,integrate-image,integrate-audio,recipe-full-setup) still make sense when read standalone — model-specific tips are preserved, only generic platform rules were extractedMade with Cursor