You found a Bilibili spreadsheet tutorial that feels unusually clear. Is it the opening explanation, the demonstrations or the checks after each step? Turn that impression into specific observations before preparing a lesson for colleagues.
Search for a task with a visible outcome
Replace a broad spreadsheet topic with a question such as combining duplicate rows while retaining an amount total. Supply the required general-search parameters, including keyword, order, page and page_size, using the contract below. Review one page for genuinely relevant examples. The bound detail endpoint uses aid, so do not substitute the BV parameter from a different endpoint.
Identify the learner's decision points
Watch the original and note when it explains the input, demonstrates an action and checks the result. Without a supplied transcript, make viewing notes rather than claiming the detail request transcribed the video. Ask what the learner knows at each point and where they might still become stuck.
Reproduce the task with your own example
Prepare a small table containing duplicates, blanks and an amount column. Follow the steps and compare the outcome with your expectation. A worksheet can include source, teaching action, learner question, reproduction result and unresolved condition. Fill in results only after actually doing the exercise; AI should not invent successful checks.
Adapt the structure using your materials
Perhaps showing a wrong result first explains the problem effectively, or perhaps frequent checks make the process clearer. Use that observation to structure your own lesson with your data and wording. Engagement is not proof of teaching quality, and software versions may differ. The outcome is a lesson outline with a verified exercise, not an automatic video score or a copied script.
Requests used in this project
- Get general search data:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_general_search · Documentation
- Get single video detail:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_detail · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_general_search
| Parameter | Type | Required | Meaning |
|---|---|---|---|
keyword |
string | Yes | Search keyword |
order |
string | Yes | Order method |
page |
integer | Yes | Page number |
page_size |
integer | Yes | Number per page |
duration |
integer | No | Duration filter |
pubtime_begin_s |
integer | No | Start date (10-digit timestamp) |
pubtime_end_s |
integer | No | End date (10-digit timestamp) |
Run the Python example
Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.
import os
import requests
# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_general_search"
params = {
"keyword": "火影忍者",
"order": "totalrank",
"page": "1",
"page_size": "42"
}
response = requests.get(
url, params=params, timeout=30,
headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload) # Inspect the actual response before mapping fields
Endpoint documentation · Free profile tool
API calls use your TRMesh account allowance. Check the endpoint price before running a script.