← anyVideoCONTENT HISTORY
WHAT CHANGED
Update to anyVideo
Snapshot Oct 24, 2026 · 13:46 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save anyVideo and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Turn one YouTube tutorial into a practical learning cycle with a viewing goal, a user-reported takeaway, a small exercise, and feedback on the user's attempt. Use when the user wants to practise or apply something learned from a video. Ground video-specific work in text or takeaways shared in chat. Do not use for an ordered curriculum, automatic video analysis, or observation-panel coaching.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 267
}
],
"name": "watch-and-apply",
"skill_md_contents": "---\nname: watch-and-apply\ndescription: Turn one YouTube tutorial into a practical learning cycle with a viewing goal, a user-reported takeaway, a small exercise, and feedback on the user's attempt. Use when the user wants to practise or apply something learned from a video. Ground video-specific work in text or takeaways shared in chat. Do not use for an ordered curriculum, automatic video analysis, or observation-panel coaching.\n---\n\n# Watch and Apply\n\n## Inputs\n\nEstablish the skill the user wants to practise and what a successful small result\nwould look like. Reuse the current video or a supplied link when available.\nAccount for the user's starting level, available materials, and time for practice.\nAsk a focused question only if these details materially affect the exercise.\n\n## Workflow\n\n1. Define one achievable learning goal. If discovery is needed, call\n `search-videos` with `{ query, reason? }`, read its `results`, and choose a\n tutorial whose title and description plausibly support that goal. Explain\n the metadata basis without claiming the tutorial's method has been verified.\n Refine an unsuitable search once before asking for a link or narrower goal.\n2. Call `display-video` with `{ videoId, reason? }` for the selected or supplied\n video. Extract the ID from a YouTube link when needed. Continue the viewing\n step only for `status: ready` with a video. For `invalid_video_id`,\n `video_not_found`, or a tool error, explain the issue and offer another returned\n candidate or work from material the user provides.\n3. Give a short viewing brief: the goal and two things to pay attention to.\n Frame these as questions for the learner, not claims about scenes or steps\n that the model has seen. Invite the user to return with their main takeaway,\n one unclear point, or the method they want to try. End the response here.\n4. Resume when the user supplies that input. Separate their account of the video\n from general subject knowledge. Ask for a missing step or pasted excerpt if\n reproducing the specific method would otherwise require guessing.\n5. Design one small exercise using the reported method and the user's constraints.\n State the task, a concrete completion criterion, and what result the user can\n share for feedback. Label any exercise devised from general knowledge as an\n assistant-proposed exercise rather than something taken from the video.\n6. Review the user's attempt against the stated criterion. Explain one useful\n correction and offer one retry or extension. Base feedback only on the work\n they share; do not claim to observe their practice or the video's demonstration.\n\n## Deliverable\n\nProvide a viewing brief, then a practical exercise, then focused feedback as the\nuser supplies the needed information. Preserve the learning goal across turns\nwithout inventing takeaways, attempts, or completion.\n\n## Boundaries\n\n- Use ordinary playback and chat. Do not require tagging, observation logs,\n transcripts, private widget state, or a playback-completion signal.\n- Do not watch, pause, seek, or advance the player on the user's behalf. A\n displayed video is not evidence that the user watched or understood it.\n- Treat the discussion button as a title-only handoff; ask for the user's\n takeaway when it provides no account of the content.\n- Use only the registered tool arguments; do not add exercise, duration, or\n playback parameters. Keep the exercise in chat, without promising saved progress.\n- If the user explicitly requests text only or no video display, call neither\n tool and build the practice cycle from the information they supply.\n"
}SHA-256 of public snapshot: 70b8679eee2d1ace3cf145b00616f6654d14a308ed7cd42e60d236c33daaebea