polym-help

name	polym-help
version	0.2.2
description	Onboarding guide for Polym — what it does, how to install it, common use cases, and how to contribute new skills. Trigger when a user seems lost, asks what this is, or asks how to get started.
metadata	{"requires":{"bins":[]}}

polym-help — Onboarding Guide

Answer any question a new SA might have about the Polym: what it does, how to set it up, what to use it for, and how to contribute.

Trigger Scenarios

• "What is polym?"
• "How do I use this?"
• "How do I get started?"
• "help"
• "What can you do?"
• "How do I install this?"
• "How do I add a skill?"
• "What skills are available?"
• "polym help"
• User seems confused about what the system does

---

Section 1 — What Is Polym?

The one-sentence pitch

Polym is a curated collection of AI skills for BytePlus SAs. Install once, and Claude Code becomes your daily assistant for IM digests, meeting summaries, customer research, and more — all connected to a shared knowledge base.

The big picture

Daily signals                Processed by skill       Saved to
─────────────────────────────────────────────────────────────────
Lark group chats      →  polym-im-digest          →  knowledge base
Live meetings         →  polym-meeting-recorder   →  knowledge base
Lark VC / Minutes     →  polym-meeting-summary    →  knowledge base
C360 usage data       →  polym-dashboard-watch    →  knowledge base (on demand)
Lark documents        →  polym-lark-doc-ingest    →  knowledge base

knowledge base
  └── polym-sa-wiki (Lark Bitable + Wiki)    ← shared SA team wiki
  └── local wiki (~/sa-wiki/)         ← your private local copy

Consumer skills
  polym-customer-brief   →  pulls everything about one customer before a meeting

Common daily scenarios

Scenario	Skill	Example phrase
Morning: catch up on yesterday's chats	polym-im-digest	"Organize yesterday's messages"
During a meeting: record and transcribe live	polym-meeting-recorder	"Start meeting recording"
Morning: see what meetings happened	polym-meeting-summary	"Summarize yesterday's meetings"
Pre-meeting: prep for a customer	polym-customer-brief	"Give me a brief on Acme before my 2pm"
Ad-hoc: how much is X using?	polym-dashboard-watch	"How many tokens did Acme use last month?"
Ad-hoc: save a Lark doc to the wiki	polym-lark-doc-ingest	"Ingest this document"
First time: create your local wiki	polym-local-wiki-init	"Set up my local wiki"
Searching SA knowledge	polym-sa-wiki	"What do we know about AK/SK rotation?"

---

Section 2 — Installation & Setup

Step 1: Prerequisites

Make sure you have these installed:

Requirement	Check	Install
Claude Code	claude --version	claude.ai/code
gh (GitHub CLI)	gh --version	brew install gh
lark-cli	lark-cli --version	Ask your team for the installer
Python 3	python3 --version	Pre-installed on macOS

Step 2: Install the skill pack

Pick the option that matches your setup. All three do the same thing.

Option A — gh CLI (recommended)

brew install gh && gh auth login   # one-time setup if you don't have gh
gh repo clone byteplus-sa/polym /tmp/polym \
  && /tmp/polym/install.sh

Option B — SSH (if you have an SSH key on GitHub)

git clone [e-mail]:byteplus-sa/polym.git /tmp/polym \
  && /tmp/polym/install.sh

Option C — GitHub Personal Access Token (no special CLI needed)

1. Go to github.com/settings/tokens → Generate new token (classic) → scope: repo
2. Copy the token (starts with ghp_)

GITHUB_TOKEN=ghp_xxxx bash <(curl -fsSL \
  -H "Authorization: token ghp_xxxx" \
  https://raw.githubusercontent.com/byteplus-sa/polym/main/install.sh)

Note: Ask the repo owner to add you as a GitHub collaborator before installing.

The installer will:

1. Clone the repo to ~/.local/share/polym
2. Link polym CLI to ~/.local/bin/
3. Install all skills to ~/.claude/skills/

If ~/.local/bin is not in your PATH:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc

Step 3: Install only the SA MVP bundle (recommended for new users)

polym install profile:sa-mvp

This installs the core skills: polym-sa-wiki, polym-meeting-recorder, polym-meeting-summary, polym-im-digest, polym-dashboard-watch, polym-local-wiki-init, polym-customer-brief, and polym-help.

Step 4: Authorize lark-cli

The skills need lark-cli authenticated with your Lark account.

# Initialize config (first time only)
lark-cli config init

# Log in as user (required for reading chats, docs, VC)
lark-cli auth login --as user

Follow the browser prompt to authorize. After login, verify:

lark-cli im +chat-search --keyword "test" --as user

If you see results (even empty), auth is working.

Step 5: Chrome extension (for polym-dashboard-watch only)

polym-dashboard-watch queries C360 via browser automation. You need the Claude for Chrome extension:

1. Open Chrome → search "Claude" in the Chrome Web Store
2. Click Add to Chrome
3. Pin the extension in the toolbar
4. With Claude Code running, click Connect to Claude Code in the extension

Verify:

In Claude Code, say: "Check if Chrome extension is connected"

Step 5b: Syncore setup (for polym-meeting-recorder)

polym-meeting-recorder uses Syncore to capture mic + system audio.

curl -fsSL https://syncorelabs.ai/install.sh | sh
syncore login
syncore doctor

Grant microphone and Screen Recording permissions when syncore doctor asks. Reopen Claude Code after setup.

Step 6: Set up your local wiki (optional but recommended)

# In Claude Code, say:
"Set up my local wiki"
# Claude will ask where to create it (default: ~/sa-wiki)

Your local wiki stores private notes, raw snapshots, and customer intel that stays on your machine. The team Lark wiki is shared; the local wiki is yours.

Verify everything works

polym list           # shows installed skills
polym doctor         # checks dependencies

---

Section 3 — How to Use Each Skill

Once installed, invoke skills in Claude Code using natural language:

"Organize yesterday's messages"          → polym-im-digest
"Start meeting recording"                → polym-meeting-recorder
"End meeting"                            → polym-meeting-recorder
"Summarize yesterday's meetings"         → polym-meeting-summary
"Brief me on Acme before my meeting"     → polym-customer-brief
"Acme used how many tokens last month?"  → polym-dashboard-watch
"Ingest this document: <URL>"            → polym-lark-doc-ingest
"What do we know about Seedance quotas?" → polym-sa-wiki
"Set up my local wiki"                   → polym-local-wiki-init

Tips

• First run: skills ask for your local wiki path once, then remember it. You won't be asked again.
• Knowledge accumulates: the more you run polym-im-digest, polym-meeting-recorder, and polym-meeting-summary, the richer your wiki becomes, and the better polym-customer-brief gets.
• No manual filing: skills save useful outputs to the knowledge base by default. You only see the final report.
• polym-customer-brief modes: use --quick for a 5-second wiki-only brief, or --full for a 20-second brief that also pulls C360 data.

---

Section 4 — Contributing a New Skill

Quick start

# Scaffold a new skill
polym new my-skill-name

# This creates:
# skills/my-skill-name/
# ├── SKILL.md        ← the prompt/instructions Claude reads
# ├── manifest.yaml  ← governance: version, owners, deps
# ├── CHANGELOG.md
# └── tests/smoke.sh

Fill the manifest first

Edit skills/my-skill-name/manifest.yaml:

name: my-skill-name
version: 0.1.0
stage: experimental   # start here; promote to beta when stable
owners:
  - your-handle@

description_for_install: |
  One paragraph. What does this skill do and when should Claude use it?

depends_on:
  binaries:
    - lark-cli: ">=1.0.20"   # list what CLI tools are needed
  env: []                    # list required env vars

triggers:
  - "natural language phrase that invokes this skill"

Stages:

Stage	Meaning	Can be in a profile?
experimental	Contract may break	No
beta	Stable for minor version	Yes
stable	Breaking changes need deprecation window	Yes
deprecated	Warn on install; removed after 90 days	No

Write the SKILL.md

SKILL.md is what Claude reads when the skill is invoked. Write it as clear instructions:

• What triggers this skill
• Step-by-step execution flow
• What to output / write
• Safety rules

Look at skills/polym-im-digest/SKILL.md for a good example of structure.

Versioning rules (semver)

Change type	Version bump	Example
New features, backwards-compatible	Minor: 0.1.0 → 0.2.0	Added a new flag
Breaking: changed input/output contract	Major: 0.2.0 → 1.0.0	Renamed a required param
Bug fix, doc fix	Patch: 0.1.0 → 0.1.1	Fixed a wrong command

Always update CHANGELOG.md when bumping the version.

Run local lint before submitting

bash tools/lint.sh my-skill-name

This checks: required files exist, manifest fields valid, version is semver, name matches folder, no trigger collisions with other skills.

Submit a PR

git add skills/my-skill-name/
git commit -m "feat(my-skill-name): describe what it does"
git push
gh pr create --title "feat: add my-skill-name" --body "..."

CI will:

1. Run tools/lint.sh on all skills (PR gate)
2. After merge to main, auto-rebuild registry.yaml and commit it

Add to a profile (optional)

If the skill should be part of the default install bundle, add it to profiles/sa-mvp.yaml:

includes:
  - my-skill-name: "^0.1"   # only beta or stable skills

Skills must be at stage: beta or higher to be included in profiles.

---

Quick Reference

# Install
gh repo clone byteplus-sa/polym ~/.local/share/polym \
  && ~/.local/share/polym/install.sh

# Manage
polym list                        # see all available skills
polym list --installed            # see what you have
polym install profile:sa-mvp     # install the MVP bundle
polym install <skill-name>        # install one skill
polym self-update                 # update CLI/catalog only
polym update                      # update CLI + refresh installed skills
polym update profile:sa-mvp       # update CLI + refresh MVP profile
polym doctor                      # check deps & auth

# Develop
polym new <name>                  # scaffold a new skill (auto-prefixes to polym-<name>)
polym bump <name> <version>       # update SKILL.md + manifest versions
polym publish -m "feat(...)"      # lint, registry, commit, rebase, push
bash tools/lint.sh <name>               # validate before PR
bash tools/build-registry.sh            # preview registry changes