Create narrow iMessage/PTT Border-Light HyperCard style nine-grid cards in Chinese or mixed Chinese-English. Use when the user says "iMessage 九宮 HyperCard", "iMessage 九宮", "做成 iMessage 九宮", "用 iMessage 九宮 HyperCard 整理", asks for a phone-readable short card with Context below, or wants Mandala/九宮/HyperCard content formatted for blue-bubble/iMessage sharing with long links, paths, and rules moved out of the card.
npx skills add https://github.com/twhsi/skills --skill imessage-nine-grid-hypercard
Turn notes, plans, links, system status, or Mandala-style content into an iMessage-ready short card. Keep the phone card narrow and readable; put long data in a separate Context block after the card.
Context after the card.When responding in chat, put the card in a plaintext fenced block so spacing survives. When sending through an actual messaging tool, send raw text without the fence.
──────────────────.╭──────────────────╮├──────────────────┤╰──────────────────╯────────────────── line inside the card.◎ for the center when a Mandala center is needed.① to ⑧ for surrounding nodes when helpful.Context after it only when there is extra data.Use this structure as the default shape, adapting labels and details to the user's content:
╭──────────────────╮
HERMÈS/iMessage
永錫.OS ONLINE
{status}
{action}
├──────────────────┤
{short title}
+{short subtitle}
手機版:短卡在上
長資料:下放Context
[[①{node}]] 代表
Context有完整資料
├──────────────────┤
①{A} ②{B} ③{C}
{A note} {B note} {C note}
④{D} ◎ ⑤{E}
{D note} {center note} {E note}
⑥{F} ⑦{G} ⑧{H}
{F note} {G note} {H note}
╰──────────────────╯
Use Context for data that would make the card heavy:
Context
① {A}: {full detail, path, link, or rule}
② {B}: {full detail}
③ {C}: {full detail}
④ {D}: {full detail}
⑤ {E}: {full detail}
⑥ {F}: {full detail}
⑦ {G}: {full detail}
⑧ {H}: {full detail}
Skip empty Context entries. If all information fits cleanly in the card and the user did not request Context, omit the Context block.
Prefer warm, concise Chinese. Mixed Chinese-English labels are fine when they match the source material, such as TARS, Codex, Hermes, Context, Apple, or iMessage. Keep the card practical and copyable rather than decorative.
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take twhsi/imessage-nine-grid-hypercard from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.