Useful instructions.
Traceable claims.
Our guides explain a task with examples a reader can inspect. This policy describes what the byline, sources, and sample evidence mean.
Editorial ownership
The tokscripts project is responsible for the guides under “tokscripts editorial.” We do not invent individual authors, credentials, interviews, customer quotes, or independent testing.
Sources and product claims
We prefer primary documentation for file formats and client configuration. Material external claims include links to the supporting source. Implementation observations are identified as observations of our preview, rather than a test of arbitrary remote videos. We avoid unsupported speed, accuracy, traffic, and revenue claims.
AI-assisted drafting and review
Drafts may be prepared with AI assistance and the claude-blog workflow. They are checked for source support, distinct purpose, working internal links, and consistency with the actual product. Automated checks and editorial scores help identify issues; they do not predict search rankings or AI citations.
Examples and transcripts
Original sample text and illustrative agent responses are labeled. Speech is a source’s claim, not proof that the claim is true. Guides keep spoken content, on-screen text, and editorial interpretation separate.
Availability and updates
Instructions distinguish available workflows, provider-dependent features, and planned services. A live availability indicator takes precedence over an example. SRT instructions require reviewed subtitle cues; plain text with timestamp references does not supply all cue boundaries. We update a guide when its facts or method change materially. A publication date is not a claim that every platform interface was tested that day.
Corrections and questions
Report the article URL, the sentence or step, and the supporting source or reproduction through our contact page or email siyuantong7@gmail.com. The privacy policy explains data handling, and the terms explain service responsibilities.