Meetings
alirezarezvani/claude-skills
A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…
The user's 腾讯会议 via the official tmeet CLI: upcoming meetings, creating, changing or cancelling one, inviting people, then the recording, minutes, transcript and attendance.
$ npx skills add nano-muse/nanoMuse --skill tencent-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nano-muse/nanoMuse tencent-meeting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nano-muse/nanoMuse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/nanomuse/skills/builtin/tencent-meeting .claude/skills/tencent-meeting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tencent-meeting" agent skill from https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meeting into .claude/skills/tencent-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tencent-meeting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meetingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nano-muse/nanoMuse --skill tencent-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nano-muse/nanoMuse tencent-meeting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nano-muse/nanoMuse.git skills-src && mkdir -p .agents/skills && cp -r skills-src/nanomuse/skills/builtin/tencent-meeting .agents/skills/tencent-meeting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tencent-meeting" agent skill from https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meeting into .agents/skills/tencent-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tencent-meeting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nano-muse/nanoMuse --skill tencent-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nano-muse/nanoMuse tencent-meeting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nano-muse/nanoMuse.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/nanomuse/skills/builtin/tencent-meeting .cursor/skills/tencent-meeting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tencent-meeting" agent skill from https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meeting into .cursor/skills/tencent-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tencent-meeting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nano-muse/nanoMuse.git --path nanomuse/skills/builtin/tencent-meeting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nano-muse/nanoMuse --skill tencent-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nano-muse/nanoMuse tencent-meeting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nano-muse/nanoMuse.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/nanomuse/skills/builtin/tencent-meeting .gemini/skills/tencent-meeting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tencent-meeting" agent skill from https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meeting into .gemini/skills/tencent-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tencent-meeting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nano-muse/nanoMuse tencent-meetingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nano-muse/nanoMuse --skill tencent-meeting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nano-muse/nanoMuse.git skills-src && mkdir -p .github/skills && cp -r skills-src/nanomuse/skills/builtin/tencent-meeting .github/skills/tencent-meeting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tencent-meeting" agent skill from https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meeting into .github/skills/tencent-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tencent-meeting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nano-muse/nanoMuse --skill tencent-meeting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nano-muse/nanoMuse tencent-meeting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nano-muse/nanoMuse.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/nanomuse/skills/builtin/tencent-meeting .opencode/skills/tencent-meeting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tencent-meeting" agent skill from https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/tencent-meeting into .opencode/skills/tencent-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tencent-meeting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tencent-meetingThe user's 腾讯会议 via the official tmeet CLI: upcoming meetings, creating, changing or cancelling one, inviting people, then the recording, minutes, transcript and attendance.
Tencent Meeting is an agent skill from nano-muse/nanoMuse. The user's 腾讯会议 via the official tmeet CLI: upcoming meetings, creating, changing or cancelling one, inviting people, then the recording, minutes, transcript and attendance. Use when the user mentions 腾讯会议, a 会议号, a 会议链接, 纪要 or 录制, or wants a meeting set up or looked up.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: nanoMuse: an open-source personal agent for every device you own. One agent with a name and a look of its own that does things, keeps working while the app is closed, remembers… The licence is GPL-3.0.
Read from SKILL.md and the folder at commit 5379e97. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Tencent Meeting loads about 1.2k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 685 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from nano-muse/nanoMuse at commit 5379e97, republished under its GPL-3.0 licence (© nano-muse). 685 words, ~1,209 tokens.
.claude/skills/tencent-meeting/SKILL.md (or your agent's skills folder).腾讯会议 has an open platform, and tmeet, Tencent's own CLI installed with npm i -g @tencentcloud/tmeet, wraps it. This is done with shell, not on the phone's screen. Every command prints JSON; add --compact to list and query commands to keep only the fields that matter, and --format json-pretty when you want to show the user the raw answer.
shell: tmeet auth status. If the command is missing or it says the user is not logged in, say so in one line and stop: logging in is the user's job (tmeet auth login opens a browser for a QR code; on the phone, tmeet auth login --no-browser prints the link to open). Do not install it or log in for them. In a sandbox on a computer the CLI and its credentials exist only when the user shared them (sandbox.share_read_only for the tool, sandbox.share = ["~/.tmeet"] for the login); "command not found" then means those two lines are missing.
Times are ISO 8601 with the offset: 2026-09-25T14:00+08:00. Compute them from the user's words and the current date in the system prompt; when the day is ambiguous (下周三 near a weekend), say the date you took.
tmeet meeting list --compact: the meetings in progress or about to start, with 会议号 (meeting_code), subject, start and end, the join link.tmeet meeting get --meeting-id <id> --compact; by 会议号 or subject: tmeet meeting search --keyword "周例会" --compact, with --start / --end for a window.tmeet meeting list-ended --start … --end … --compact.tmeet meeting invitees-list --meeting-id <id>. Who came: tmeet report participants --meeting-id <id> --compact.tmeet record list --meeting-id <id> for the recordings; tmeet record smart-minutes --record-file-id <id> for the AI minutes; tmeet record transcript-search --record-file-id <id> --keyword "预算" to find where something was said, transcript-paragraphs to read around it. tmeet minutes search --keyword … finds 元宝纪要 by words.tmeet contact search --keyword 张三 (the enterprise directory; only when the user's account is in an enterprise).Read what the JSON says. A meeting the CLI does not return does not exist for you; do not guess a 会议号.
Every write reaches other people's calendars. Before the call, show the exact subject, date, time span and invitees and ask with one ask_user; run only what they approved.
tmeet meeting create --subject "需求评审" --start 2026-09-25T14:00+08:00 --end 2026-09-25T14:30+08:00. The answer has the 会议号 and the join link; those are what the user wants to pass on. Recurring meetings and settings (waiting room, mute on entry) are flags of the same command; tmeet meeting create --help lists them.tmeet meeting update --meeting-id <id> --subject … --start … --end …. Cancel: tmeet meeting cancel --meeting-id <id>, only when the user said to cancel that very meeting.tmeet meeting invitees-add --meeting-id <id> --userids … after contact search for the ids; invitees-remove the same way.Never use tmeet control … (calling, kicking, the waiting room) unless the user is in the meeting and asks for exactly that; never tmeet record permission-apply-commit without the user having seen the prepare preview. Sentinel shows every shell command on an approval card; that is expected.
feishu skill): one message, its text approved first. A 飞书 calendar event with the link as the location keeps both sides in step.calendar action=search); afterwards a reminder ten minutes before, or an alarm through the phone when the phone is there.meetings/YYYY-MM-DD-<slug>.md, the way the meeting-prep skill keeps a brief.Reply in a few lines: the meeting (subject, time, 会议号, link), or what was read (the next meeting and when; the three points of the minutes). Do not paste whole transcripts into the answer; give the gist and offer the rest. remember the user's usual meeting length and who they meet with most, so the next request needs fewer questions.
© nano-muse, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in nanomuse/skills/builtin/tencent-meeting of nano-muse/nanoMuse.
Open the folder on GitHubat commit 5379e97
Tencent Meeting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tencent Meeting this skillnano-muse/nanoMuse | 813 | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Meetingsalirezarezvani/claude-skills | 28k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Meeting Minutesgithub/awesome-copilot | 40k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Meeting Action ItemsNousResearch/hermes-agent | 252k | — | ~950 | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Summarize Meetingphuryn/pm-skills | 27k | — | ~749 | Automated safety check: Pass | MIT |
alirezarezvani/claude-skills
A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…
github/awesome-copilot
Generate concise, actionable meeting minutes for internal meetings.
NousResearch/hermes-agent
Turn meeting notes into cited decisions, owners, tickets. An agent skill from NousResearch/hermes-agent.
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
phuryn/pm-skills
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.
sickn33/agentic-awesome-skills
Transform messy meeting notes and transcripts into structured action items, decisions, and follow-ups.
nano-muse/nanoMuse
Places, routes, travel times, distances and weather in China through the 高德地图 (Amap) MCP server.
nano-muse/nanoMuse
Where a parcel is, when it will arrive and what a shipment would cost, through the 快递100 MCP server: any Chinese courier (顺丰, 京东, 中通, 圆通, 韵达, 邮政 and more) from a tracking number.
nano-muse/nanoMuse
Trains in China through the 12306 MCP server: routes, dates, options, connections and stops with no screen; booking only on the user's word, in the 12306 app on their phone, stopping before payment.
nano-muse/nanoMuse
Compare two to five options (products, plans, places, tools, offers) on the criteria that matter to the user, in a table the user can re-weight, with a recommendation.
nano-muse/nanoMuse
The user's 飞书 / Lark through its command-line tool (lark-cli): agenda, people and groups, reading and sending messages, events, tasks, documents, with no app open.
nano-muse/nanoMuse
Go through recent mail and sort it into needs-a-reply, waiting-on-others, to-do and can-ignore, with draft replies ready for review.
The user's 腾讯会议 via the official tmeet CLI: upcoming meetings, creating, changing or cancelling one, inviting people, then the recording, minutes, transcript and attendance. Tencent Meeting is an agent skill from nano-muse/nanoMuse. The user's 腾讯会议 via the official tmeet CLI: upcoming meetings, creating, changing or cancelling one, inviting people, then the recording, minutes, transcript and attendance.
Tencent Meeting fits situations like: the user mentions 腾讯会议; wants a meeting set up.
Run `npx skills add nano-muse/nanoMuse --skill tencent-meeting -a claude-code`. Or copy the skill folder (nanomuse/skills/builtin/tencent-meeting in nano-muse/nanoMuse) into .claude/skills/tencent-meeting in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nano-muse/nanoMuse --skill tencent-meeting -a codex`. Or copy the skill folder (nanomuse/skills/builtin/tencent-meeting in nano-muse/nanoMuse) into .agents/skills/tencent-meeting in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nano-muse/nanoMuse --skill tencent-meeting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tencent-meeting, .gemini/skills/tencent-meeting, .github/skills/tencent-meeting and .opencode/skills/tencent-meeting in your project.
Going by SKILL.md and its folder, Tencent Meeting needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Tencent Meeting is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Tencent Meeting: Meetings (alirezarezvani/claude-skills, 28k stars), Meeting Minutes (github/awesome-copilot, 40k stars), Meeting Action Items (NousResearch/hermes-agent, 252k stars) and Meeting Notes (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nano-muse (a GitHub organization) maintains it in nano-muse/nanoMuse, which has 813 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 11, 2026.
Source: nano-muse/nanoMuse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.