Document YouTube transcript limits
This commit is contained in:
@@ -30,10 +30,18 @@ The command exits non-zero on failure and writes the error to stderr.
|
||||
1. Run the `fetch_transcript` wrapper provided by this skill for the YouTube URL.
|
||||
2. Read the returned `title` and `transcript`.
|
||||
3. Build source understanding from the transcript.
|
||||
4. Respond to the user's request in chat by default.
|
||||
5. Create durable output when requested or when active project conventions require it.
|
||||
6. State the output path when you create durable output.
|
||||
7. State the scratch location when you create temporary scratch files.
|
||||
4. Notice when the transcript points to important visible material that transcript text cannot recover.
|
||||
5. Respond to the user's request in chat by default.
|
||||
6. Create durable output when requested or when active project conventions require it.
|
||||
7. State the output path when you create durable output.
|
||||
8. State the scratch location when you create temporary scratch files.
|
||||
|
||||
## Transcript-only limits
|
||||
|
||||
This skill ingests captions, not the video stream.
|
||||
It cannot recover on-screen text, diagrams, UI state, slides, prompts, file trees, terminal output, images, or gestures unless they are described in the transcript.
|
||||
If the transcript refers to visible material that may matter, mention the limitation in the response or source note.
|
||||
Examples include `as you can see`, `shown here`, `this file`, `this prompt`, `this format`, `on screen`, `look at`, or visible demos of interfaces and documents.
|
||||
|
||||
## Durable output
|
||||
|
||||
|
||||
Reference in New Issue
Block a user