Show why nine is not prime
Use a concept video when a visual comparison will help more than a recording. Review the finished video in ngram. This example teaches the rule; it does not show a product screen.
Start in Cursor with the change you need to explain. Give ngram an approved summary, specify the viewer and review the quote. Open the resulting project to check what the video shows before sharing it.
Use a concept video when a visual comparison will help more than a recording. Review the finished video in ngram. This example teaches the rule; it does not show a product screen.
Remove internal IDs and paste only the detail that customers need. Open the result and check the label against the shipped export. Share after the release owner approves.
This setup uses the public local plugin. You can follow it without finding a marketplace listing.
Download the public repository. Copy the contents of cursor-plugin, including its hidden .cursor-plugin directory, into ~/.cursor/plugins/local/ngram. Reload the window. If local plugins are restricted, ask the workspace administrator to allow this installation.
Open Customize → Plugins and select the local ngram plugin. Authenticate the ngram server and sign in to the account whose credits should pay for the video.
Give the agent an approved change summary and a viewer. Ask it to preview the settings and cost. Confirm only when the scope fits; keep the job ID and project link.
Ask about the existing job or open the project. Verify that the steps match the release. If exact screens matter, supply an approved capture or record the workflow in Studio.
The plugin connects to the full ngram MCP server and includes skills for creating videos and business images.
Give the agent a change summary or public article and tell it what the viewer needs to understand.
The plugin’s video skill previews settings and cost before you approve creation.
Ask about the job you already started; use the project link for later review.
Open the project when a scene needs an edit or when you need to inspect the timeline.
Start here when the explanation begins with an approved engineering detail. Use a recording for exact UI and a written note for commands people need to copy.
Help a new engineer see why seven is prime and nine is not. Check that the narration and diagram agree before sending the lesson.
See the explainer playbookShow account admins the new due-date column in an export. Check the final label against a real export before announcing the change.
See the changelog playbookTurn the invitation sequence into a short brief for the support team. If the learner needs to match a button exactly, use an approved recording.
See the help center playbookOnce the agent returns a project, review the script, narration and visuals against your approved source.
Use visuals to explain a relationship that the source describes.
Explore featureReview the narration in Studio for important technical terms.
See featureCheck the spoken explanation against the source passage.
See featureEdit the project after inspecting it in ngram.
See featureUse a diagram when the relationship is easier to see than hear.
See featureCheck captions for names, acronyms and technical vocabulary.
See featureUse Studio for a branded variant after the explanation is reviewed.
See featureCreate a separate language version when the audience needs it.
See featureUse a release note for a change summary or an approved capture when viewers need to recognize the screen.
Open these tools when the project needs additional editing or you already have source material outside the editor.
Give a specific audience a reason to watch and a source against which you can check the explanation.
Explain a technical concept with a public reference developers can verify.
Give product teammates an example that clarifies an unfamiliar mechanism.
Explain the idea behind a product before asking someone to watch its demo.
Introduce an approved concept before a customer training session.
Explain a recurring question, keeping exact steps in the help article.
Adapt a public release note into a concept explanation for a new audience.
Use GitHub for an in-thread reply, a browser extension for a public page, or a connected assistant for a conversational request.
Choose ChatGPT when a reader needs a narrated explanation from supplied text in an eligible workspace.
Explore ChatGPTRequest a video where the pull request, issue or release supplies the product context.
Explore the GitHub AppStart from the open page when its content belongs in a video brief.
Explore the Chrome extensionStart from a repeatable event when the request needs to run outside chat.
Explore the Zapier integrationCursor plugin Local editor | Direct MCP setup Without plugin skills | ngram Studio Project workspace | Zapier Event automation | |
|---|---|---|---|---|
| Where it starts | Cursor conversation | Compatible MCP client | ngram Studio | Approved trigger record |
| Source | Approved change summary or public source | Sources supported by the connected profile | Project brief and source files | Mapped trigger fields |
| Creative choices | Plugin previews settings and cost | Full profile without bundled Cursor skills | Project and editor settings | Fields exposed by the action |
| Best fit | Explain a change before handing it to a reviewer | Create and edit in a compatible assistant | Demonstrate actual product screens | Route recurring drafts for review |
FAQ
Still curious? Build a walkthrough from Cursor
Install the local plugin, sign in to ngram and start with a single change your reviewer needs to understand.