SYSU Anything Apple

Use when the user wants the macOS 12+ Apple-enhanced SYSU workflow layer, especially natural-language requests such as 把课表同步到日历、把雨课堂 ddl 加到提醒事项、把宣讲会或招聘会写进日历、...

Security Scan

The package is internally consistent: it is a macOS-only wrapper that delegates Apple Calendar/Reminders work to a local sysu-anything binary installed from npm and the instructions and install steps match that purpose.

Purpose & Capability

Name/description, required binary (sysu-anything-apple), and the npm install target (sysu-anything) align with the declared purpose of adding an Apple Calendar/Reminders layer to the SYSU-Anything CLI. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

SKILL.md instructs the agent to invoke the local sysu-anything-apple binary and to check SYSU login state and run 'apple doctor'. That scope is appropriate for the stated goal, but the runtime will read/write the local state directory (~/.sysu-anything) and invoke CLI commands that may access networked SYSU services and trigger macOS Calendar/Reminders permissions. The skill delegates sensitive actions (auth, remote signups, writes to Apple apps) to the installed binary rather than doing them itself.

Install Mechanism

Install is an npm package (sysu-anything) which is a standard distribution mechanism for this kind of tooling. npm installs are moderate-risk (third-party code executed on install). The included deploy script only copies files into a target skill bundle or codex skills folder. No downloads from obscure URLs or archive extraction were found.

Credentials

The skill declares no required environment variables or external credentials, which is coherent. However, it uses a local state dir (~/.sysu-anything) and runtime commands may prompt for or use cached credentials (e.g., workwechat auth) or read session files. The deploy script also honors CODEX_HOME when targeting codex. Users should expect the CLI to need campus service logins and to request macOS Calendar/Reminders permissions.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. The deploy script writes skill files only into the chosen target (codex skills dir or a portable bundle) and does not modify other skills or global agent configs beyond copying files into the target location.

Assessment

This skill appears coherent: it is a macOS-specific front-end that calls a local sysu-anything binary to sync campus items into Apple Calendar and Reminders. Before installing, consider: (1) npm packages run code on your machine—verify the upstream repo (https://github.com/qybaihe/SYSU-Anything) and review releases if you do not already trust it; (2) the runtime will read/write ~/.sysu-anything and may require campus service logins (workwechat, jwxt, etc.), so expect local session files and possible network activity; (3) on first use macOS will prompt to allow Calendar/Reminders access—only grant if you trust the tool; (4) if you deploy into a shared agent runtime (codex/CodexHome), be aware the skill files are copied into that runtime's skills directory. If any of these behaviors are unacceptable, do not install or run the package. If you want lower risk, run the CLI manually in an isolated environment and inspect its behavior before granting permissions.

Use the published macOS Apple entrypoint instead of re-deriving EventKit flows. Prefer the installed sysu-anything-apple binary. If it is missing, install the compiled package with npm i -g sysu-anything. If the user is actively developing the local repo, the checked-out workspace build is also acceptable.

This skill is for macOS 12+ (Monterey+) only. The published Apple native bridge supports both Apple Silicon and Intel. On non-macOS or macOS 11 and below, keep using sysu-anything-cli; only the Apple Calendar / Apple Reminders layer is unavailable.

sysu-anything-apple

First step

1. Confirm the runtime path:
   • preferred: sysu-anything-apple
   • install if missing: npm i -g sysu-anything
   • local-dev fallback inside the repo: npm run build
   • supported host: macOS 12+ only
   • unsupported host fallback: use sysu-anything without Apple sync
   • if the user previously installed an older npm runtime, ask them to upgrade sysu-anything before retrying Apple sync
2. Prefer targeted help before composing a command:
   • sysu-anything-apple --help
   • sysu-anything-apple <command> --help
   • sysu-anything-apple <command> <subcommand> --help
3. Always verify the Mac-side bridge first:
   • sysu-anything-apple apple doctor
4. Check the SYSU-side login state before the real action:
   • qg: no login check needed
   • ykt homework list/detail --reminders: sysu-anything ykt status
   • today / jwxt timetable / jwxt leave apply: sysu-anything jwxt status
   • career teachin detail/jobfair detail --calendar --reminders: no SYSU login check needed
   • career teachin signup/jobfair signup --confirm --calendar --reminders: if the command still needs to seed career-session.json, run sysu-anything auth workwechat first
   • gym book: sysu-anything gym profile
   • libic reserve: sysu-anything libic whoami
   • usc classroom submit --confirm --calendar --reminders: sysu-anything usc whoami --json
   • explore seminar reserve: sysu-anything explore whoami
   • xgxt workstudy apply --calendar: sysu-anything xgxt current-user
5. If the check fails, restore login first, rerun the check, then run the Apple sync command.

The Apple entrypoint reuses the same state directory:

~/.sysu-anything/

Routing

• If you need the command map or examples, read references/overview.md.
• For Apple-specific career teachin/jobfair import and signup-sync behavior, read references/career.md.
• For Apple-specific libic reservation sync behavior, read references/libic.md.
• Prefer --json when another agent or script needs structured output.

Closed Loops

• today --calendar
• jwxt timetable --calendar [--calendar-scope week|term]
• qg link --calendar --reminders
• career teachin detail --calendar --reminders
• career teachin signup --confirm --calendar --reminders
• career jobfair detail --calendar --reminders
• career jobfair signup --confirm --calendar --reminders
• ykt homework list --reminders
• ykt homework detail --reminders
• gym book --confirm --calendar --reminders
• libic reserve --confirm --calendar --reminders
• usc classroom submit --confirm --calendar --reminders
• usc classroom sync --calendar --reminders
• explore seminar reserve --confirm --calendar --reminders
• jwxt leave apply --confirm --calendar-block --reminders
• xgxt workstudy apply --confirm --calendar [--calendar-start-date <YYYY-MM-DD>] [--calendar-weeks <n>]

Safety

• qg link --calendar --reminders creates a planned trip in Apple apps; it does not mean the ticket is confirmed.
• career teachin/jobfair detail --calendar --reminders is local import only; it does not touch the remote signup state.
• career teachin/jobfair signup without --confirm stays in preview mode and skips Apple sync; use the corresponding detail command if the user only wants local Calendar / Reminders import.
• gym book, libic reserve, usc classroom submit, explore seminar reserve, jwxt leave apply, and xgxt workstudy apply only perform real writes with --confirm.
• usc classroom submit --calendar --reminders writes Apple items only after BPM /site/app/start returns OK. The initial app_id=197 application usually has no concrete classroom yet; Apple notes should say the room is pending later allocation.
• usc classroom sync --calendar --reminders only backfills local Apple items from an already-existing BPM session. It does not call /site/app/start.
• ykt homework list/detail --reminders defaults to future deadlines only; add --include-past when the user explicitly wants overdue items imported too.
• xgxt workstudy apply --calendar writes the submitted work-study time template into Apple Calendar; because xgxt payloads only contain weekday + time, the Apple layer defaults to expanding 1 week unless --calendar-weeks is provided.
• Run apple doctor before the first sync on a new Mac or after macOS permission changes.