HiNoter

View saved version →

---
name: browse-hinoter-files
description: Browse the workspaces, files, and tasks accessible to the authenticated HiNoter user. Use when the user asks to view all workspaces, list files, find files by workspace, or query tasks; do not use for modifying, deleting, or generating file content.
---

# Browse HiNoter Workspaces and Files

Use the plugin MCP service tools `list_user_workspaces`, `list_workspace_files`, and `list_user_tasks` to browse the current user's data scope.

1. Call `list_user_workspaces` once first. Do not pass `user_id`, access tokens, or any other identity information. The server identifies the user from the OAuth context and returns only the personal workspace and the team workspaces where the current user has an active membership.
2. When files are needed, call `list_workspace_files` for the target workspace using the `id` from the workspace results; the personal workspace always uses `personal`. The default page size is 50; when `has_more` is `true` in the results, continue reading with the same `workspace_id` and an increasing `offset`, with a single `limit` no larger than 100.
3. The file list contains only metadata and the `has_summary` flag — no transcriptions, summary content, images, todos, storage paths, or sharing credentials. When the user wants a summary, use `get_user_file_summary` with an explicit `id` from the list.
4. When the user wants tasks, use `list_user_tasks` with the workspace `id`; the optional `status` accepts `all` or `todo`, and the optional `assignee_scope` accepts `all` or `my`.
5. If the workspace, file, or task tool returns `isError`, briefly restate the error and stop. Do not try other workspace IDs and do not bypass permission checks by calling regular business APIs.
6. When the corresponding MCP tools are not available in the current task, do not interpret it as "no workspaces or files". Explain that the HiNoter MCP is not loaded in the current task, give the following troubleshooting order, then stop:
   - In the Codex plugin settings, confirm HiNoter is enabled; from the command line, use `codex plugin list` to confirm both `installed` and `enabled` are `true` for `hinoter`.
   - After installing, updating, or enabling the plugin, start a new task (restart Codex if necessary); existing tasks do not hot-load new MCP tools.
   - If a new task still has no tools, check that the MCP URL in the plugin `mcp.json` is reachable and that the protected resource metadata and authorization server metadata return JSON. The server must have `mcp.issuer`, `mcp.resource_uri`, and `mcp.token_hmac_key` configured; production also requires `mcp.web_login_url` with test authorization disabled.
   - Do not fall back to unauthorized network requests, and do not assume the user's identity or manually pass `user_id` or access tokens.

This skill only reads workspace, file, and task data. It never creates, updates, or deletes anything, never generates summaries, and never reads transcriptions.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: get-file-summary
description: Retrieve an existing summary for a single file accessible to the authenticated HiNoter user. Use when the user asks to view or read a HiNoter file summary and provides a file_id or a clear file_id exists in context; do not use for generating, updating, or deleting summaries.
---

# Get File Summary

Use the `get_user_file_summary` tool provided by the plugin MCP service to read an existing summary.

1. Obtain a unique, explicit `file_id` from the user message or a trusted previous tool result. If there is no `file_id`, ask first; if the user only provides a file name, use `$browse-hinoter-files` to get a list first, then ask the user to confirm the single match. Never guess identifiers.
2. Call `get_user_file_summary` exactly once using the `file_id`; do not pass `user_id`, access tokens, or any other identity information. The server determines the current user from the OAuth context and validates read permission on the personal or team workspace.
3. 当 `has_summary` 为 `true` 时，保留 Markdown 结构展示返回的总结；可以提及文件名称。不要编造工具未返回的事实或更新时间。
4. When `has_summary` is `false`, clearly state that the file has no existing summary. Never generate or fabricate a summary.
5. If the tool returns `isError`, briefly restate the error and stop. Do not try other file IDs and do not bypass permission checks by calling regular business APIs.
6. When `get_user_file_summary` is not available in the current task, do not interpret it as "the file has no summary". Explain that the HiNoter MCP is not loaded in the current task, then advise: confirm HiNoter is enabled in the Codex plugin settings (from the command line, check `codex plugin list`), and start a new task or restart Codex after installing or updating the plugin. If a new task still has no tools, check that the MCP URL in the plugin `mcp.json` is reachable and that the protected resource metadata and authorization server metadata return JSON, and confirm the server has `mcp.issuer`, `mcp.resource_uri`, and `mcp.token_hmac_key` configured — production also requires `mcp.web_login_url` with test authorization disabled. Do not fall back to unauthorized network requests.

This skill only reads existing summaries. It never triggers regeneration, never reads transcriptions, images, todos, or storage paths, and never performs any write operation.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: get-file-transcription
description: Retrieve an existing transcription for a single file accessible to the authenticated HiNoter user. Use when the user asks to view or read a HiNoter file transcription and provides a file_id or a clear file_id exists in context; do not use to initiate a new transcription.
---

# Get File Transcription

Use the `get_user_file_transcription` tool provided by the plugin MCP service to read an existing transcription.

1. Obtain a unique, explicit `file_id` from the user message or a trusted previous tool result. If there is no `file_id`, ask first; if the user only provides a file name, use `$browse-hinoter-files` to get a list first, then ask the user to confirm the single match. Never guess identifiers.
2. Call `get_user_file_transcription` exactly once using the `file_id`; do not pass `user_id`, access tokens, or any other identity information.
3. Present the returned `transcription` or `segments` as-is. Do not add content the tool did not return, and do not interpret empty content as a transcription failure.
4. If the tool returns `isError`, briefly restate the error and stop. Do not bypass permission checks by calling regular business APIs.

This skill only reads existing transcriptions. It never triggers new transcriptions, never reads summaries, images, todos, or storage paths, and never performs any write operation.

View saved version →

---
name: list-user-tasks
description: Query tasks in the personal or team workspaces accessible to the authenticated HiNoter user. Use when the user asks to list all tasks, incomplete tasks, or tasks assigned to them; do not use for creating, modifying, or completing tasks.
---

# Query HiNoter Tasks

Use the `list_user_tasks` tool provided by the plugin MCP service to query tasks.

1. Determine `workspace_id` from a trusted `list_user_workspaces` result; the personal workspace always uses `personal`. Never guess team workspace IDs.
2. Use `status` = `all` for all tasks or `todo` for incomplete tasks; use `assignee_scope` = `my` for tasks assigned to the current user, otherwise `all`.
3. Each read covers 20 matching files by default; when `has_more` is `true`, continue reading with the same filters and an increasing `offset`, with a single `limit` no larger than 100.
4. Do not pass `user_id`, access tokens, or any other identity information. The server identifies the user from the OAuth context and validates read permission on the personal or team workspace.
5. If the tool returns `isError`, briefly restate the error and stop. Do not bypass permission checks by calling regular business APIs.

This skill only reads tasks. It never creates, updates, deletes, completes, or regenerates anything.