Mobile Native
leepokai/Codync
Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed.
A skill your agent uses when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends.
$ npx skills add different-ai-studio/teamclu --skill sentry-monitor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install different-ai-studio/teamclu sentry-monitor --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/different-ai-studio/teamclu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sentry-monitor .claude/skills/sentry-monitor && 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 "sentry-monitor" agent skill from https://github.com/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitor into .claude/skills/sentry-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-monitor", 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/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitorType 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 different-ai-studio/teamclu --skill sentry-monitor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install different-ai-studio/teamclu sentry-monitor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai-studio/teamclu.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/sentry-monitor .agents/skills/sentry-monitor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sentry-monitor" agent skill from https://github.com/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitor into .agents/skills/sentry-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-monitor", 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 different-ai-studio/teamclu --skill sentry-monitor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install different-ai-studio/teamclu sentry-monitor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai-studio/teamclu.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/sentry-monitor .cursor/skills/sentry-monitor && 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 "sentry-monitor" agent skill from https://github.com/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitor into .cursor/skills/sentry-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-monitor", 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/different-ai-studio/teamclu.git --path .claude/skills/sentry-monitor--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 different-ai-studio/teamclu --skill sentry-monitor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install different-ai-studio/teamclu sentry-monitor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai-studio/teamclu.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/sentry-monitor .gemini/skills/sentry-monitor && 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 "sentry-monitor" agent skill from https://github.com/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitor into .gemini/skills/sentry-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-monitor", 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 different-ai-studio/teamclu sentry-monitorInstalls 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 different-ai-studio/teamclu --skill sentry-monitor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/different-ai-studio/teamclu.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/sentry-monitor .github/skills/sentry-monitor && 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 "sentry-monitor" agent skill from https://github.com/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitor into .github/skills/sentry-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-monitor", 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 different-ai-studio/teamclu --skill sentry-monitor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install different-ai-studio/teamclu sentry-monitor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai-studio/teamclu.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sentry-monitor .opencode/skills/sentry-monitor && 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 "sentry-monitor" agent skill from https://github.com/different-ai-studio/teamclu/tree/main/.claude/skills/sentry-monitor into .opencode/skills/sentry-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-monitor", 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.
sentry-monitorA skill your agent uses when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends.
Sentry Monitor is an agent skill from different-ai-studio/teamclu. Use when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends. Triggers on "sentry 监控", "sentry 日报", "查看 sentry", "sentry report", "sentry monitor".
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile. It works with Sentry, Rust and iOS. The repository describes itself as: TeamClu, AI Agent Desktop Workspace. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8f754b3. 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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From 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.
Sentry Monitor loads about 1.7k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 773 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 different-ai-studio/teamclu at commit 8f754b3, republished under its MIT licence (© different-ai-studio). 773 words, ~1,668 tokens.
.claude/skills/sentry-monitor/SKILL.md (or your agent's skills folder).Scan the TeamClu Sentry projects for unresolved fatal/high issues, analyze root causes, and report.
| Project | Sentry Slug | Platform |
|---|---|---|
| Web / desktop frontend | ucar-inc/teamclu-react | JavaScript React |
| Desktop Rust process | ucar-inc/teamclu-rust | Rust |
| iOS | ucar-inc/teamclu-ios | apple-ios |
| Expo | ucar-inc/teamclu-expo | react-native |
ucar-inc/teamclu (the old Rust slug) does not exist — it was deleted, and
sentry issue list 404s on it. teamclu-rust replaced it on 2026-09-04, so
that project has no history before then; an empty result there is expected for a
while rather than a signal. Re-verify with sentry project list ucar-inc/ --json
if a scan errors on an unknown project.
The org is on Sentry's free tier: 5,000 errors/month, onDemandMaxSpend = 0,
billing period resetting on the 19th. When the quota runs out Sentry drops
every incoming event silently — from the issue list that looks identical to
"no new errors." This has already happened twice (2026-08-17 and 2026-09-02),
and the second time the projects sat blind for over two weeks.
Never report "全部正常" without clearing this check.
sentry api "/organizations/ucar-inc/stats_v2/?field=sum(quantity)&groupBy=outcome&category=error&statsPeriod=7d&interval=1d"Read the accepted and rate_limited series:
accepted non-zero for the most recent day → ingestion is healthy, continue.accepted at 0 with rate_limited climbing → quota exhausted. Stop the
normal report. Lead with this instead, get the exact numbers from
sentry api "/customers/ucar-inc/" (categories.errors: usage /
reserved / usageExceeded, plus billingPeriodEnd), and say plainly that
the issue list below is stale as of the last accepted event.Run these in parallel, one per project:
sentry issue list ucar-inc/teamclu-react --query "is:unresolved" --period 48h --json --fields shortId,title,priority,level,status --limit 30
sentry issue list ucar-inc/teamclu-rust --query "is:unresolved" --period 48h --json --fields shortId,title,priority,level,status --limit 30
sentry issue list ucar-inc/teamclu-ios --query "is:unresolved" --period 48h --json --fields shortId,title,priority,level,status --limit 30
sentry issue list ucar-inc/teamclu-expo --query "is:unresolved" --period 48h --json --fields shortId,title,priority,level,status --limit 30Use --period for the time window (24h / 48h / 14d), not a lastSeen:
clause. Default is 90 days, which is far wider than a daily report wants.
Filter results: keep only issues where level is fatal OR priority is
high.
--fields gotcha (CLI 0.26.1): count, userCount, firstSeen and
lastSeen are listed in --help but are silently dropped from issue list
output — you get the key omitted, not an error. Volume and recency have to come
from sentry issue view <shortId> --json, which does return them. Do not report
event counts sourced from issue list.
If no issues match and step 0 was clean, skip to step 4 with the "全部正常" message. If step 0 was not clean, say so instead — an empty list under an exhausted quota means nothing.
For each filtered issue (max 10 total), perform local root cause analysis:
sentry issue view <shortId> --jsonFrom the stack trace / error message, identify the relevant source files and functions in the codebase.
Read those source files to understand the code context around the error site.
Produce a one-sentence root cause summary based on the stack trace + source.
Two things worth checking before writing the summary:
metadata.value
across the filtered set and treat identical values as one root cause rather
than reporting the same bug three times.culprit is a repo path (/src/...) rather than a bundle
(assets/index-*.js) — it names the file directly.When there are more than ~4 issues to analyze, run them as parallel subagents
via the Agent tool; each runs sentry issue view, reads the relevant sources,
and returns one sentence. For fewer than that, just do it inline — spawning
agents costs more than it saves.
If analysis cannot determine a root cause, use the error title as-is and say the root cause is undetermined. Do not guess.
Sentry 日报 <YYYY-MM-DD>
【Web / 桌面】N 个高优 issue
• <shortId> [<level>] <title> — 根因:<root cause summary>
• ...
【桌面 Rust】N 个高优 issue
• ...
【iOS】N 个高优 issue
• ...
【Expo】N 个高优 issue
• ...
修复命令:/sentry-fix <top-issue-id>Omit any project section with zero matching issues. When step 0 found the quota exhausted, put that first, above every section:
⚠️ Sentry 配额已耗尽(<usage>/<reserved>),<date> 起事件全部被丢弃,<billingPeriodEnd> 重置。
以下列表停留在最后一条被接收的事件,不代表当前状态。Present the report in the conversation.
Pushing to WeCom is a separate step that needs the user's go-ahead, unless
this run is the scheduled daily report (/loop 24h /sentry-monitor), where
pushing is the whole point. When the user asked for an analysis rather than a
daily report, show the report and offer to push — do not push unasked, since it
posts to a group chat.
wecom-cli msg send_message '{"chat_type": 2, "chatid": "wrOOClYgAA5gMJijxEUfWC6M0RAjwlWQ", "msgtype": "text", "text": {"content": "<report text>"}}'If no fatal/high issues exist anywhere and the quota gate was clean:
Sentry 日报 <YYYY-MM-DD> — 全部正常,无高优 issue/sentry-monitor/loop 24h /sentry-monitorsentry CLI is not authenticated, prompt the user to run sentry auth login.sentry command through tail/head when you care about
success — the pipeline's exit code is the pager's, so a failed call reads as
exit 0. Redirect to a file and check $?.© different-ai-studio, MIT. 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 .claude/skills/sentry-monitor of different-ai-studio/teamclu.
Open the folder on GitHubat commit 8f754b3
Sentry Monitor 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 |
|---|---|---|---|---|---|---|
| Sentry Monitor this skilldifferent-ai-studio/teamclu | 167 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Mobile Nativeleepokai/Codync | 269 | 1 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Ccapwysaid/CameraCapture | 191 | — | ~1.4k | Automated safety check: Pass | MIT | |
| iOS Log DiagnoseUniClipboard/UniClipboard | 1.9k | — | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Add Error Trackinggotempsh/temps | 833 | — | ~4.2k | Automated safety check: Notes | Apache-2.0 | |
| Frb Dev Envfzyzcjy/flutter_rust_bridge | 5.4k | — | ~5.5k | Automated safety check: Pass | MIT |
leepokai/Codync
Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed.
wysaid/CameraCapture
Install or use the ccap CLI for camera capture, webcam inspection, device listing, frame capture, and video metadata.
UniClipboard/UniClipboard
Drive the UniClipboard iOS app in a simulator and read its OSLog yourself to diagnose a mobile-sync bug, instead of asking the user to paste logs.
gotempsh/temps
Add Temps error tracking to applications using the Sentry-compatible SDK.
fzyzcjy/flutter_rust_bridge
A skill your agent uses when the user wants Docker-based FRB development or Tart-based iOS Simulator validation.
getsentry/sentry-for-ai
Full Sentry SDK setup for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS).
different-ai-studio/teamclu
A skill your agent uses when implementing TeamClu platform sign-in, organization-role access, employee pages or protected data endpoints in an app, or changing its login permissions.
different-ai-studio/teamclu
Create a workspace role that follows the ROLE.md specification.
different-ai-studio/teamclu
生成图片:配图、插图、海报、头像、示意图、Logo 草稿、封面、banner。触发词:画一张、画个、生成图片、生成一张图、做张图、做个图、配图、出图、生图、AI 绘图、image、draw、illustration、poster。仅从零生成,不做已有图片的编辑或修改。
different-ai-studio/teamclu
Control macOS desktop applications: open/operate apps, click buttons, type text, scroll, keyboard shortcuts, window management, toggle options, dropdown selections, etc.
different-ai-studio/teamclu
A skill your agent uses when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error.
different-ai-studio/teamclu
Control Windows desktop applications: open/operate apps, click controls, type text, scroll, keyboard shortcuts, window management, toggle options, lists and combos, etc.
Categories
A skill your agent uses when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends. Sentry Monitor is an agent skill from different-ai-studio/teamclu. Use when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends.
Sentry Monitor fits situations like: the user wants to check Sentry issues; run a Sentry daily report; monitor error trends.
Run `npx skills add different-ai-studio/teamclu --skill sentry-monitor -a claude-code`. Or copy the skill folder (.claude/skills/sentry-monitor in different-ai-studio/teamclu) into .claude/skills/sentry-monitor in your project. Claude Code loads it when a task matches its description.
Run `npx skills add different-ai-studio/teamclu --skill sentry-monitor -a codex`. Or copy the skill folder (.claude/skills/sentry-monitor in different-ai-studio/teamclu) into .agents/skills/sentry-monitor 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 different-ai-studio/teamclu --skill sentry-monitor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-monitor, .gemini/skills/sentry-monitor, .github/skills/sentry-monitor and .opencode/skills/sentry-monitor in your project.
SKILL.md names no scripts, command-line tools or credentials: Sentry Monitor is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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.
Sentry Monitor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Sentry Monitor: Mobile Native (leepokai/Codync, 269 stars), Ccap (wysaid/CameraCapture, 191 stars), iOS Log Diagnose (UniClipboard/UniClipboard, 1.9k stars) and Add Error Tracking (gotempsh/temps, 833 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
different-ai-studio (a GitHub organization) maintains it in different-ai-studio/teamclu, which has 167 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 11, 2026.
Source: different-ai-studio/teamclu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.