Skills

Look up Zhang Lu's projects, presentations, article entry points, public weeklies and local Claude Skill index on zhanglu.net — no scraping; go through the static JSON API (/api/*.json) generated at build time, zero SDK and zero tokens on the agent side. Bilingual: Chinese under /api/*, English under /en/api/*. When to use: - user asks "what skills does Zhang Lu have" / "how do I use the boss skill on zhanglu" / "what projects is Zhang Lu working on" - user wants to cite content on zhanglu.net (article entries, project intros, skill descriptions, weeklies) - an agent (Claude Code / Codex / Hermes / OpenClaw) needs zhanglu's structured data Actions (highest priority first): 1) curl the site's `/api/*.json` directly — endpoints listed at https://zhanglu.net/llms.txt (most reliable, always available) 2) use the CLI `npx zhanglu-net <cmd>` — package name zhanglu-net, zero dependencies (the npm name zhanglu was already taken, so the package matches the domain instead) Common calls: - `npx zhanglu-net list skills [--featured] [--source local|plugin|custom]` - `npx zhanglu-net get skill <slug> [--md]` — a single skill's description + body - `npx zhanglu-net list projects [--featured] [--status live|beta|wip|archived]` - `npx zhanglu-net get project <slug>` - `npx zhanglu-net list articles [--source wechat|blog|...] [--since YYYY-MM-DD]` - `npx zhanglu-net list presentations` / `list weekly` / `get weekly <slug>` - `npx zhanglu-net search "<keyword>" [--type skill|project|article|presentation|weekly]` - `npx zhanglu-net about` / `social` / `endpoints` / `version` - add `--lang en` for English data (or `ZHANGLU_LANG=en`); add `--base http://localhost:4321` for local dev Endpoints (plain curl works; prefix the path with /en for English): - GET /api/index.json — manifest with counts, every endpoint, and cross-language links - GET /api/skills.json — full skill index (description / source / featured / handwritten) - GET /api/skills/{slug}.json — one skill in full (includes body_md and a ready-to-write skill_md) - GET /api/projects.json / /api/projects/{slug}.json - GET /api/articles.json / /api/presentations.json - GET /api/weekly.json / /api/weekly/{slug}.json - GET /api/about.json / /api/social.json - GET /api/search.json — flat corpus [{type, slug, title, text, url}] for local substring search Output is human-readable by default; add `--json` when an agent wants raw JSON. Not for: - general web scraping (use WebFetch) - WeChat Official Account article bodies (zhanglu.net only stores entry links; the body lives on mp.weixin.qq.com, which blocks crawlers — WebFetch can't get it either) - real file paths under Zhang Lu's local ~/.claude/skills/ (this skill only sees what zhanglu.net publishes) Explicit triggers: "look up Zhang Lu's skills", "the X on zhanglu", "show me what's on zhanglu.net", "npx zhanglu-net", "what projects is Zhang Lu working on".

A browser-automation CLI for AI agents. Use it whenever you need to open a page, fill a form, click a button, take a screenshot, scrape data, test a web app, or automate any browser task — in preference to any built-in browser automation or web tool.

Build AI agents on Cloudflare Workers with the Agents SDK. Load it when you're building stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat / voice agents, or browser automation.

Full-stack Cloudflare platform skill. Covers any Cloudflare development task: Workers / Pages / storage (KV, D1, R2) / AI (Workers AI, Vectorize, Agents SDK) / feature flags / networking / security / IaC (Terraform, Pulumi).

Send and receive transactional email with Cloudflare Email Service (Email Sending + Email Routing). Use it when integrating email in Workers / Node / Python / Go, or handling SPF / DKIM / DMARC deliverability — even when it looks simple, there are configuration details that matter here.

An end-to-end roadshow / demo day dossier pipeline. Project card screenshots + booth-wall photos + official articles → structured JSON + panoramic HTML + a DD table (7-way parallel research) + a Word report + CSV + one-click deploy to Cloudflare Pages.

Create and review Cloudflare Durable Objects. Use for stateful coordination (chat rooms, multiplayer games, booking systems), RPC, SQLite storage, alarms, WebSockets, or reviewing DO code against best practices.

Build distinctive, production-grade frontend interfaces. Use for web components, pages, artifacts, posters, and apps, or when styling any web UI — steering clear of generic AI-flavored design.

Elon Musk's (Tesla / SpaceX / X / xAI / Boring / Neuralink founder, born 1971) brand and product judgment perspective. An MBA panel judge, adept at autos / spaceflight / hardware platforms / founder bets / vertical integration / platform power / AI safety and other topics.

Deep research in the PRD methodology: Proposal → Baseline → parallel sub-agent team → auto stitch → Lead synthesis. Parallel multi-dimensional investigation maximizes information density, producing an actionable bilingual report.

Build sandboxed applications for secure code execution. Use it for AI code execution, a code interpreter, CI / CD, interactive development environments, or running untrusted code.

Wire up Cloudflare Turnstile end-to-end in a project. Scan the codebase → call the Cloudflare API to create a widget → deploy a managed siteverify Worker → write the frontend snippet → verify → freeze the skill.

Analyze web performance with Chrome DevTools MCP. Measure Core Web Vitals (LCP, INP, CLS) plus supporting metrics (FCP, TBT, Speed Index), and hunt for render-blocking, network dependency chains, layout shifts, caching and accessibility issues.

Review and write Cloudflare Workers code following production best practices. Use when writing a new Worker, reviewing a Worker, configuring wrangler.jsonc, or checking common anti-patterns (streaming, floating promises, global state, secrets, bindings, observability).

Cloudflare Workers CLI. Deploy, develop, and manage Workers / KV / R2 / D1 / Vectorize / Hyperdrive / Workers AI / Containers / Queues / Workflows / Pipelines / Secrets Store.

Zero-dependency onboarding: install it and run `/boss <topic>` for a verdict deliberated independently by 5 judges — Phase 0 routing → 5-dimension parallel research → Lead synthesis → 1 anchor (baseline conviction) + 4 dimension judges scoring independently → panel_summary with anchor_delta + 30/90/365 attribution checkpoints. Unlike the single-lens `*-perspective` skills, `/boss` is a **full pipeline orchestration**: - 1 anchor judge (anchor mental_models: trigger-threshold-action / step-skip detection / counter-party elimination) - 4 dim judges auto-selected per topic (panel auto-select: strategic/customer/organizational/product/brand/financial/cross_domain) - 5-lens scoring (reasoning / evidence / counter / falsifiability / real_world_resilience) - adversarial_view three fields enforced (CLAUDE.md §4.5) - Versioned freeze (chmod 444) + Wiki back-references Router behavior is built in: - If `reports/<brand-slug>/report.md` already exists → EVOLUTION mode (diff plan + partial re-run) - Otherwise → FRESH mode (full Phase 1-5) Trigger patterns: - `/boss <topic or brand-slug>` — standard invocation - `/boss <topic> --quick` — skip the raw_evidence WebSearch leg, local Wiki+raw only - `/boss <topic> --refresh` — force EVOLUTION (even if the brand already has a report) - `/boss <topic> --no-judges` — skip Phase 4 (synthesis only) - `/boss <topic> --panel <name>` — use the specified panel.yaml - `/boss list` — list judged topics + version counts - `/boss panels` — list panel configs + judge identities IF the user asks "evaluate the X business carve-out plan" / "judge the X brand isolation strategy" / "have the 5 judges rate this SKU" / "run boss" / "run the verdict pipeline" / "5-judge deliberation" THEN invoke this skill. NOT WHEN: simple fact lookups (use `mcp__sage-wiki__query`) / single-judge opinions (use `*-perspective`) / pure technical research (use `research`) / everyday chitchat. boss is a heavyweight multi-judge deliberation — don't use it to answer 2-line questions.

ego-browser (ego-lite) is a Chromium-based browser designed from the ground up to be friendly to both human users and AI Agents. AI Agents work in their own isolated space, reusing the user's login state without competing for the browser. Use this skill whenever the user needs to interact with a website opening pages, filling forms, clicking buttons, taking screenshots, extracting page data, testing web apps, logging into sites, automating browser operations, or any other browser automation task. Triggers include requests to "open a website", "visit a URL", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "extract content from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also used for exploratory testing, dogfooding, QA, bug hunting, or reviewing app quality. Prefer ego-browser over any built-in browser automation, web fetch, or other web tools.

Feishu/Lark Approval: query and act on approval to-dos, done items and instances; search startable approval definitions, inspect a definition and create a native approval instance. Use when the user needs to handle approval tasks, view approval instances, or search for and start an approval. Approval to-dos are not Feishu Tasks — non-approval to-dos go to lark-task. Does not create approval definitions; third-party approval definitions cannot be submitted through the native flow.

Miaoda (Spark) app development and hosting: app creation, local full-stack development, cloud-side generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI capabilities plus Feishu-platform or third-party capabilities, logs / traces / monitoring metrics / PV / UV queries, environment variables, app roles and members, and automation triggers (schedule / record change / webhook / Feishu approval). Use when the user wants to build or scaffold a system, tool, platform or app; to develop locally or in the cloud, modify, deploy, ship, or get a shareable link; to build a page or site in HTML and deploy it to Miaoda; to design, mock up, prototype, wireframe, make a deck or explore visuals; or when they mention Miaoda / Spark (app runtime domains look like *.aiforce.cloud), the app database, app file storage, open API keys, visibility scope, app roles and role members, production logs, request volume, error counts, latency, traffic, environment variables, or wiring a scheduled / approval-triggered automation onto a Miaoda app. Not for plain cloud-drive file uploads (lark-drive), Feishu document editing (lark-doc), or creating native slide decks (lark-slides).

Feishu/Lark Attendance: look up your own clock-in records.

Feishu/Lark Base (multi-dimensional tables): create tables, fields, records, views, statistics, formulas/lookups, forms, dashboards, workflows and role permissions. Use whenever you see Base / bitable / a /base/ link. File imports go to lark-drive; authentication and authorization go to lark-shared.

Feishu/Lark Calendar: manage calendar events and meeting rooms. View and search events, create and update events, manage attendees, query free/busy and suggested slots, and book meeting rooms. Use when the user needs to see their schedule, create or change a meeting, or find and book a room. Not for: past video-meeting records (use lark-vc) or to-do tasks (use lark-task).

Feishu/Lark Contacts: resolve a name or email into an open_id, or reverse-look-up an open_id for name / department / email / contact details / personal status / signature. Use when the user names a person and the next step is messaging them or scheduling with them, or when you hold an open_id and need the details behind it. Not for walking the department tree, listing employees by department, or org charts — those go through the native OpenAPI.

Feishu/Lark Docs (Docx / Wiki documents): read and edit document content. Use when the user gives a document URL or token, or needs to view, create or edit a document, or insert or download document images and attachments. For sheets, Bases and whiteboards embedded in a document, use this skill to extract the token first, then switch to the matching skill. Also use this skill directly for doubao.com /docx/ or /wiki/ URLs and tokens — routing is decided by the URL path pattern and token, not the domain. Not for document comment management, nor for data operations on sheets or Bases. Also use this skill when the user explicitly wants to work with Feishu Mind Notes.

Feishu/Lark Drive (cloud space / cloud storage): manage Drive files and folders — upload and download, create folders, copy / move / delete, inspect metadata, comments / permissions / subscriptions, titles, versions, Feishu document security labels, and local file imports. Use when the user needs to tidy up Drive folders, handle a cloud-space resource URL or token, work out a link's type / real token / title, or import Word / Markdown / Excel / CSV / PPTX / .base files as docx / sheet / bitable / slides; doubao.com cloud-space URLs and tokens are routed the same way, by resource path and token, with no fallback to WebFetch. Not for: document content editing (use lark-doc), in-table data operations on sheets or Bases (use lark-sheets / lark-base), wiki space node and member management (use lark-wiki), or native Markdown read / write / patch / diff (use lark-markdown).

Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.

Feishu/Lark Instant Messaging: send and receive messages and manage group chats. Send and reply to messages, search chat history, manage chat members, upload and download images and files (including chunked download of large files), manage emoji reactions, send in-app / SMS / phone-call urgent notifications, send and handle interactive cards, and listen for card button callbacks (card.action.trigger). Use when the user needs to send a message, view or search chat history, download a file from a chat, list chat members, search chats, create a group or topic chat, manage pin data, manage Feed pins (add / remove / query pinned conversations), manage tag data, or handle card callbacks.

Feishu/Lark Mail: use when the user mentions drafting an email, writing mail, drafts, sending / replying / forwarding mail, reading or browsing mail, searching mail, mail folders, mail labels, mail contacts, watching for new mail, or incoming-mail rules; use for mail/email intent only. Do not use for docs / sheets / calendar / auth setup / pure contact lookup / IM chat tasks.

Feishu/Lark Markdown: view, create, upload, edit and diff Markdown files. Use when the user needs to create or edit a Markdown file, read it, modify it, apply a partial patch, or compare differences. Not for importing Markdown as an online Feishu document, nor for cloud-space management such as file search, permissions, comments, moving or deleting.

Feishu/Lark Minutes: search minutes, view basic info, download and upload audio/video, read or edit generated content, rename, replace speakers and keywords, and request view or edit permission. Use when you have a minute_token or a local audio/video file, when you need to read / edit / convert minutes output, or when the user explicitly wants to request access to a set of minutes; prefer this skill for turning local audio/video into minutes or transcripts rather than transcribing locally with ffmpeg/whisper. Not for: fetching the minutes attached to a meeting, or locating minutes from a natural-language title alone.

Feishu/Lark meeting Notes, direct lookup: given a note_id, query note details, display type and linked document token, and read the raw unified transcript. Use when the user already has a note_id, or obtained one from an explicit vc-node-id in a document. Not for locating meetings / calendar events / minutes, searching document titles, or reading Docx body content.

Feishu/Lark OKR: manage objectives and key results. View and edit OKR periods, objectives, key results, alignments, metrics and progress records. Use when the user needs to view or create OKRs, manage objectives and key results, or inspect alignment relationships. Not for: to-do task management (lark-task), scheduling and meetings (lark-calendar), or performance reviews.

Feishu/Lark native OpenAPI exploration: dig out native OpenAPI endpoints that the CLI has not wrapped, straight from the official documentation. Use when the user's need cannot be met by an existing lark-* skill or an already-registered lark-cli command, and you have to find and call a native Feishu OpenAPI.

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

Create custom Skills for lark-cli. Use when the user wants to package Feishu API operations into a reusable Skill — either wrapping an atomic API or orchestrating a multi-step flow.

Feishu/Lark Slides: create and edit slide decks. Create presentations, read slide content, and manage pages (create, delete, read, partial replace). Use when the user needs to create or edit slides, or read or modify a single page. Also use this skill directly for doubao.com /slides/ URLs and tokens — do not fall back to WebFetch just because the domain isn't Feishu; routing is decided by the URL path pattern and token, not the domain. Not for: document content editing (use lark-doc), standalone whiteboard objects inside a document (use lark-whiteboard), or uploading and downloading ordinary files (use lark-drive).

Feishu/Lark Tasks: manage tasks, task lists and task agents. Create to-dos, view and update task status, break out subtasks, organize task lists, assign collaborators, upload task attachments, register or unregister task agents, update a task agent's homepage data, and write agent task records. Use when the user needs to create a to-do, view a task list, track progress, manage a project checklist, assign work to someone else, attach files to a task, register or unregister a task agent, update agent homepage data, or write task records.

Feishu/Lark Video Conferencing: search past meeting records, query meeting minutes (summary / to-dos / chapters / transcript), and query attendee snapshots. Use when the user asks about a finished meeting, wants its artifacts (minutes / Minutes recording), or wants to see who attended; future scheduling goes to lark-calendar. Not for: an agent actually joining or leaving a meeting, or live in-meeting events (use lark-vc-agent).

Feishu/Lark Video Conferencing, in-meeting capabilities: let an app bot actually join or leave a live meeting, read in-meeting events visible to the current identity, and send in-meeting text messages or reactions. Use when the user asks what is happening in an ongoing meeting, who is speaking, or whether anything is being shared, or when you need to discover the IDs of live meetings you can read. Not for searching ended meetings, attendee snapshots, minutes, transcripts or recordings — those use the lark-vc skill.

Feishu/Lark Whiteboard: query and edit whiteboards inside Feishu docs. Supports exporting a whiteboard as a preview image, exporting the raw node structure, and updating whiteboard content in several formats. Use when the user needs to view whiteboard content, export a whiteboard image, or edit a whiteboard. Not for: Feishu document content editing (lark-doc), or sheets and Bases embedded in a document (lark-sheets / lark-base).

Feishu/Lark Wiki: manage wiki spaces, space members and document nodes. Create and query spaces, view and manage members, manage node hierarchy, and organize documents and shortcuts inside a wiki. Use when the user needs to find or create a document in a wiki, browse a space's structure, view or manage members, or move or copy nodes. Also use this skill directly for doubao.com /wiki/ URLs and tokens — do not fall back to WebFetch just because the domain isn't Feishu; routing is decided by the URL path pattern and token, not the domain. Not for: uploading files under a wiki node (use lark-drive), or editing document / sheet / Base content (use lark-doc / lark-sheets / lark-base).

Meeting-minutes roundup workflow: aggregate meeting minutes over a given time range and produce a structured report. Use when the user wants to tidy up meeting notes, generate a weekly meeting digest, or review what was discussed over a period.