@bohuyeshan/openagent-labforge-core 3.11.2 → 3.11.4

package/generated/skills-bundles/paper/skills/productivity/communication/auto-claude__feishu-notify/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: "auto-claude/feishu-notify"
+description: "Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says \"发飞书\", \"notify feishu\", or other skills need to send status updates."
+argument-hint: ["message-text"]
+allowed-tools: "Bash(curl *), Bash(cat *), Read, Glob"
+metadata:
+  category: "productivity/communication"
+---
+
+# Feishu/Lark Notification
+
+Send a notification: **$ARGUMENTS**
+
+## Overview
+
+This skill provides Feishu/Lark integration for ARIS. It is designed as an **internal utility** — other skills call it at key events (experiment done, review scored, checkpoint waiting). It can also be invoked manually.
+
+**Zero-impact guarantee**: If no `feishu.json` config exists, this skill does nothing and returns silently. All existing workflows are completely unaffected.
+
+## Configuration
+
+The skill reads `~/.claude/feishu.json`. If this file does not exist, **all Feishu functionality is disabled** — skills behave exactly as before.
+
+### Config Format
+
+```json
+{
+  "mode": "push",
+  "webhook_url": "https://open.feishu.cn/open-apis/bot/v2/hook/YOUR_WEBHOOK_ID",
+  "interactive": {
+    "bridge_url": "http://localhost:5000",
+    "timeout_seconds": 300
+  }
+}
+```
+
+### Modes
+
+| Mode | `"mode"` value | What it does | Requires |
+|------|----------------|--------------|----------|
+| **Off** | `"off"` or file absent | Nothing. Pure CLI as-is | Nothing |
+| **Push only** | `"push"` | Send webhook notifications at key events. Mobile push, no reply | Feishu bot webhook URL |
+| **Interactive** | `"interactive"` | Full bidirectional. Approve/reject from Feishu, reply to checkpoints | [feishu-claude-code](https://github.com/joewongjc/feishu-claude-code) running |
+
+## Workflow
+
+### Step 1: Read Config
+
+```bash
+cat ~/.claude/feishu.json 2>/dev/null
+```
+
+- **File not found** → return silently, do nothing
+- **`"mode": "off"`** → return silently, do nothing
+- **`"mode": "push"`** → proceed to Step 2 (push)
+- **`"mode": "interactive"`** → proceed to Step 3 (interactive)
+
+### Step 2: Push Notification (webhook)
+
+Send a rich card to the Feishu webhook:
+
+```bash
+curl -s -X POST "$WEBHOOK_URL" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "msg_type": "interactive",
+    "card": {
+      "header": {
+        "title": {"tag": "plain_text", "content": "TITLE"},
+        "template": "COLOR"
+      },
+      "elements": [
+        {"tag": "markdown", "content": "BODY"}
+      ]
+    }
+  }'
+```
+
+**Card templates by event type:**
+
+| Event | Title | Color | Body |
+|-------|-------|-------|------|
+| `experiment_done` | Experiment Complete | `green` | Results table, delta vs baseline |
+| `review_scored` | Review Round N: X/10 | `blue` (≥6) / `orange` (<6) | Score, verdict, top 3 weaknesses |
+| `checkpoint` | Checkpoint: Waiting for Input | `yellow` | Question, options, context |
+| `error` | Error: [type] | `red` | Error message, what failed |
+| `pipeline_done` | Pipeline Complete | `purple` | Final summary, deliverables |
+| `custom` | Custom | `blue` | Free-form message from $ARGUMENTS |
+
+**Return immediately after curl** — push mode never waits for a response.
+
+### Step 3: Interactive Notification (bidirectional)
+
+Interactive mode uses [feishu-claude-code](https://github.com/joewongjc/feishu-claude-code) as a bridge:
+
+1. **Send message** to the bridge:
+   ```bash
+   curl -s -X POST "$BRIDGE_URL/send" \
+     -H "Content-Type: application/json" \
+     -d '{"type": "EVENT_TYPE", "title": "TITLE", "body": "BODY", "options": ["approve", "reject", "custom"]}'
+   ```
+
+2. **Wait for reply** (with timeout):
+   ```bash
+   curl -s "$BRIDGE_URL/poll?timeout=$TIMEOUT_SECONDS"
+   ```
+   Returns: `{"reply": "approve"}` or `{"reply": "reject"}` or `{"reply": "user typed message"}` or `{"timeout": true}`
+
+3. **On timeout**: Fall back to `AUTO_PROCEED` behavior (proceed with default option).
+
+4. **Return the user's reply** to the calling skill so it can act on it.
+
+### Step 4: Verify Delivery
+
+- **Push mode**: Check curl exit code. If non-zero, log warning but do NOT block the workflow.
+- **Interactive mode**: If bridge is unreachable, fall back to push mode (if webhook configured) or skip silently.
+
+## Helper Function (for other skills)
+
+Other skills should use this pattern to send notifications:
+
+```markdown
+### Feishu Notification (if configured)
+
+Check if `~/.claude/feishu.json` exists and mode is not "off":
+- If **push** mode: send webhook notification with event summary
+- If **interactive** mode: send notification and wait for user reply
+- If **off** or file absent: skip entirely (no-op)
+```
+
+**This check is always guarded.** If the config file doesn't exist, the skill skips the notification block entirely — zero overhead, zero side effects.
+
+## Event Catalog
+
+Skills send these events at these moments:
+
+| Skill | Event | When |
+|-------|-------|------|
+| `/run-experiment` | `experiment_done` | Screen session finishes |
+| `/idea-discovery` | `checkpoint` | Between phases (if interactive) |
+| `/idea-discovery` | `pipeline_done` | Final report ready |
+| `/monitor-experiment` | `experiment_done` | Results collected |
+| `/research-pipeline` | `checkpoint` | Between workflow stages |
+| `/research-pipeline` | `pipeline_done` | Full pipeline complete |
+
+## Key Rules
+
+- **NEVER block a workflow** because Feishu is unreachable. Always fail open.
+- **NEVER require Feishu config** — all skills must work without it.
+- **Config file absent = mode off.** No error, no warning, no log.
+- **Push mode is fire-and-forget.** Send curl, check exit code, move on.
+- **Interactive timeout = auto-proceed.** Don't hang forever waiting for a reply.
+- **Respect `AUTO_PROCEED`**: In interactive mode, if the user doesn't reply within timeout, use the same auto-proceed logic as the calling skill.
+- **No secrets in notifications.** Never include API keys, tokens, or passwords in Feishu messages.

package/generated/skills-bundles/paper/skills/productivity/visual-design/auto-claude__pixel-art/SKILL.md

@@ -0,0 +1,138 @@
+---
+name: "auto-claude/pixel-art"
+description: "Generate pixel art SVG illustrations for READMEs, docs, or slides. Use when user says \"画像素图\", \"pixel art\", \"make an SVG illustration\", \"README hero image\", or wants a cute visual."
+argument-hint: ["description of what to draw"]
+allowed-tools: "Write, Edit, Read, Bash(open *)"
+metadata:
+  category: "productivity/visual-design"
+---
+# Pixel Art SVG Generator
+
+Create a pixel art SVG illustration: $ARGUMENTS
+
+## Design Principles
+
+### Pixel Grid
+- Each "pixel" is a `<rect>` with width/height of 7px
+- Grid spacing: 7px (no gaps between pixels)
+- Characters are typically 8-10 pixels wide, 8-12 pixels tall
+- Use `<g transform="translate(x,y)">` to position and reuse character groups
+
+### Color Palette
+Keep it simple — 3-5 colors per character:
+- **Skin**: `#FFDAB9` (light), `#E8967A` / `#D4956A` (blush/shadow)
+- **Eyes**: `#333`
+- **Hair**: `#8B5E3C` (brown), `#2C2C2C` (black), `#FFD700` (blonde), `#C0392B` (red)
+- **Clothes**: use project's brand color (e.g. `#4A9EDA` for blue, `#74AA63` for green)
+- **Shoes/pants**: `#444`
+- **Accessories**: `#555` (glasses frames), `#FFD700` (crown)
+
+### Character Template (7px grid)
+```
+Row 0 (hair top):     4 pixels centered
+Row 1 (hair):         6 pixels wide
+Row 2 (face top):     6 pixels — all skin
+Row 3 (eyes):         6 pixels — skin, eye, skin, skin, eye, skin
+Row 4 (mouth):        6 pixels — skin, skin, mouth, mouth, skin, skin
+Row 5 (body top):     8 pixels — hand, 6 shirt, hand
+Row 6 (body):         6 pixels — all shirt
+Row 7 (legs):         2+2 pixels — with gap in middle
+```
+
+### Scene Composition
+
+#### Chat Dialogue Layout (like our hero image)
+- Two characters on left/right sides, vertically centered
+- Chat bubbles between them, alternating left/right
+- Bubble tails point toward the speaking character
+- Arrows between bubbles show direction of communication
+- Use `orient="auto"` markers for arrow heads
+- Bottom: tagline or decoration
+
+#### Single Character with Label
+- Character centered
+- Label text below
+- Optional: speech bubble above
+
+#### Group Scene
+- Characters spaced evenly
+- Optional: ground line, background elements
+- Keep viewBox tight — no wasted space
+
+### SVG Structure
+```xml
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 W H" font-family="monospace">
+  <defs>
+    <!-- Arrow markers if needed -->
+  </defs>
+
+  <rect width="W" height="H" fill="#fafbfc" rx="12"/>  <!-- Background -->
+
+  <!-- Characters via <g transform="translate(...)"> -->
+  <!-- Dialogue bubbles: <rect> + <polygon> tail + <text> -->
+  <!-- Arrows: <line> with marker-end -->
+  <!-- Labels: <text> with text-anchor="middle" -->
+</svg>
+```
+
+### Chat Bubble Recipe
+```xml
+<!-- Blue bubble (left character speaks) -->
+<rect x="110" y="29" width="280" height="26" fill="#e8f4fd" stroke="#4a9eda" stroke-width="1.5" rx="8"/>
+<!-- Tail pointing left toward character -->
+<polygon points="108,41 99,47 108,46" fill="#e8f4fd" stroke="#4a9eda" stroke-width="1.5"/>
+<rect x="107" y="40" width="3" height="7" fill="#e8f4fd"/>  <!-- covers stroke at junction -->
+<text x="123" y="46" font-size="13px">📄 Message here</text>
+
+<!-- Orange bubble (right character responds) -->
+<rect x="490" y="71" width="280" height="26" fill="#fdf2e8" stroke="#da8a4a" stroke-width="1.5" rx="8"/>
+<!-- Tail pointing right toward character -->
+<polygon points="772,83 781,89 772,88" fill="#fdf2e8" stroke="#da8a4a" stroke-width="1.5"/>
+<rect x="770" y="82" width="3" height="7" fill="#fdf2e8"/>
+<text x="503" y="88" font-size="13px">🤔 Response here</text>
+```
+
+### Arrow Recipe
+```xml
+<defs>
+  <marker id="ar" markerWidth="8" markerHeight="6" refX="8" refY="3" orient="auto">
+    <polygon points="0 0, 8 3, 0 6" fill="#4a9eda"/>
+  </marker>
+</defs>
+<!-- Right arrow (→): x1 < x2 -->
+<line x1="392" y1="42" x2="465" y2="42" stroke="#4a9eda" stroke-width="2" marker-end="url(#ar)"/>
+<!-- Left arrow (←): x1 > x2 -->
+<line x1="488" y1="84" x2="420" y2="84" stroke="#da8a4a" stroke-width="2" marker-end="url(#ar-o)"/>
+```
+
+## Workflow
+
+### Step 1: Understand the Request
+- What characters/objects to draw?
+- What's the scene? (dialogue, portrait, group, diagram)
+- What colors/brand to match?
+- What size? (compact for badge, wide for README hero)
+
+### Step 2: Generate SVG
+- Write to a temp file or project directory
+- Open with `open <file.svg>` for preview
+- Keep viewBox tight — measure actual content bounds
+
+### Step 3: Iterate with User
+- User provides feedback on screenshot
+- Common fixes: overlap, arrow direction, spacing, sizing
+- Use `Edit` for small tweaks, `Write` for major redesigns
+- Typical: 2-4 iterations to get it right
+
+### Step 4: Finalize
+- Ensure no personal info in the SVG
+- Clean up: remove unused defs, tighten viewBox
+- Suggest adding to README: `![Alt text](filename.svg)`
+
+## Common Pitfalls
+- **Arrow direction**: `orient="auto"` follows line direction. Line going right→left = arrowhead points left
+- **Bubble overlap**: keep 38-44px vertical spacing between rows
+- **Text overflow**: monospace 13px ≈ 7.8px/char, emoji ≈ 14px. Measure before setting bubble width
+- **Character overlap with bubbles**: keep character x-zone and bubble x-zone separated by ≥10px
+- **viewBox too large**: match viewBox to actual content, add ~10px padding
+- **Tail stroke artifact**: always add a small `<rect>` at the bubble-tail junction to cover the stroke line

package/generated/skills-bundles/paper/skills/research/document-authoring/auto-claude__paper-compile/SKILL.md

@@ -0,0 +1,252 @@
+---
+name: "auto-claude/paper-compile"
+description: "Compile LaTeX paper to PDF, fix errors, and verify output. Use when user says \"编译论文\", \"compile paper\", \"build PDF\", \"生成PDF\", or wants to compile LaTeX into a submission-ready PDF."
+argument-hint: ["paper-directory"]
+allowed-tools: "Bash(*), Read, Write, Edit, Grep, Glob"
+metadata:
+  category: "research/document-authoring"
+---
+# Paper Compile: LaTeX to Submission-Ready PDF
+
+Compile the LaTeX paper and fix any issues: **$ARGUMENTS**
+
+## Constants
+
+- **COMPILER = `latexmk`** — LaTeX build tool. Handles multi-pass compilation automatically.
+- **ENGINE = `pdflatex`** — LaTeX engine. Options: `pdflatex` (default), `xelatex` (for CJK/custom fonts), `lualatex`.
+- **MAX_COMPILE_ATTEMPTS = 3** — Maximum attempts to fix errors and recompile.
+- **PAPER_DIR = `paper/`** — Directory containing LaTeX source files.
+- **MAX_PAGES** — Main body page limit (to end of Conclusion, excluding references & appendix). ICLR=9, NeurIPS=9, ICML=8.
+
+## Workflow
+
+### Step 1: Verify Prerequisites
+
+Check that the compilation environment is ready:
+
+```bash
+# Check LaTeX installation
+which pdflatex && which latexmk && which bibtex
+
+# If not installed, provide instructions:
+# macOS: brew install --cask mactex-no-gui
+# Ubuntu: sudo apt-get install texlive-full
+# Server: conda install -c conda-forge texlive-core
+```
+
+Verify all required files exist:
+
+```bash
+# Must exist
+ls $PAPER_DIR/main.tex
+
+# Should exist
+ls $PAPER_DIR/references.bib
+ls $PAPER_DIR/sections/*.tex
+ls $PAPER_DIR/figures/*.pdf 2>/dev/null || ls $PAPER_DIR/figures/*.png 2>/dev/null
+```
+
+### Step 2: First Compilation Attempt
+
+```bash
+cd $PAPER_DIR
+
+# Clean previous build artifacts
+latexmk -C
+
+# Full compilation (pdflatex + bibtex + pdflatex × 2)
+latexmk -pdf -interaction=nonstopmode -halt-on-error main.tex 2>&1 | tee compile.log
+```
+
+### Step 3: Error Diagnosis and Auto-Fix
+
+If compilation fails, read `compile.log` and fix common errors:
+
+**Missing packages:**
+```
+! LaTeX Error: File `somepackage.sty' not found.
+```
+→ Install via `tlmgr install somepackage` or remove the `\usepackage` if unused.
+
+**Undefined references:**
+```
+LaTeX Warning: Reference `fig:xyz' on page 3 undefined
+```
+→ Check `\label{fig:xyz}` exists in the correct figure environment.
+
+**Missing figures:**
+```
+! LaTeX Error: File `figures/fig1.pdf' not found.
+```
+→ Check if the file exists with a different extension (.png vs .pdf). Update the `\includegraphics` path.
+
+**Citation undefined:**
+```
+LaTeX Warning: Citation `smith2024' undefined
+```
+→ Add the missing entry to `references.bib` or fix the citation key.
+
+**`[VERIFY]` markers in text:**
+→ Search for `[VERIFY]` markers left by `/paper-write`. These indicate unverified citations or facts. Search for the correct information or flag to the user.
+
+**Overfull hbox:**
+```
+Overfull \hbox (12.5pt too wide) in paragraph at lines 42--45
+```
+→ Minor: usually ignorable. If severe (>20pt), rephrase the text or adjust figure width.
+
+**BibTeX errors:**
+```
+I was expecting a `,' or a `}'---line 15 of references.bib
+```
+→ Fix BibTeX syntax (missing comma, unmatched braces, special characters in title).
+
+**`\crefname` undefined for custom theorem types:**
+→ Ensure `\crefname{assumption}{Assumption}{Assumptions}` and similar are in the preamble after `\newtheorem{assumption}`.
+
+### Step 4: Iterative Fix Loop
+
+```
+for attempt in 1..MAX_COMPILE_ATTEMPTS:
+    compile()
+    if success:
+        break
+    parse_errors()
+    auto_fix()
+```
+
+For each error:
+1. Read the error message from `compile.log`
+2. Locate the source file and line number
+3. Apply the fix
+4. Recompile
+
+### Step 5: Post-Compilation Checks
+
+After successful compilation, verify the output:
+
+```bash
+# Check PDF exists and has content
+ls -la main.pdf
+# Check page count
+pdfinfo main.pdf | grep Pages
+
+# macOS: open for visual inspection
+# open main.pdf
+```
+
+**Automated checks:**
+
+- [ ] PDF file exists and is > 100KB (not empty/corrupt)
+- [ ] Total page count is reasonable (MAX_PAGES + appendix + references)
+- [ ] No "??" in the PDF (undefined references — grep the log)
+- [ ] No "[?]" in the PDF (undefined citations — grep the log)
+- [ ] Figures are rendered (not missing image placeholders)
+
+```bash
+# Check for undefined references
+grep -c "LaTeX Warning.*undefined" compile.log
+
+# Check for missing citations
+grep -c "Citation.*undefined" compile.log
+```
+
+### Step 6: Page Count Verification
+
+**CRITICAL**: Verify main body fits within MAX_PAGES.
+
+Main body = first page through end of Conclusion section (not necessarily §5 — could be §6, §7, or §8 depending on structure).
+References and appendix are NOT counted.
+
+**Precise check using `pdftotext`:**
+```bash
+# Extract text and find where Conclusion ends vs References begin
+pdftotext main.pdf - | python3 -c "
+import sys
+text = sys.stdin.read()
+pages = text.split('\f')
+for i, page in enumerate(pages):
+    if 'Ethics Statement' in page or 'Reproducibility' in page:
+        print(f'Conclusion ends on page {i+1}')
+    if any(w in page for w in ['References', 'Bibliography']):
+        lines = [l for l in page.split('\n') if l.strip()]
+        for l in lines[:3]:
+            if 'References' in l or 'Bibliography' in l:
+                print(f'References start on page {i+1}')
+                break
+"
+```
+
+If Conclusion ends mid-page and References start on the same page, the main body is that page number (e.g., if both are on page 9, main body = ~8.5 pages, which is fine for a 9-page limit since it leaves room for the References header).
+
+If over limit:
+- Identify which sections are longest
+- Suggest specific cuts (move proofs to appendix, compress tables, tighten writing)
+- Report: "Main body is X pages (limit: MAX_PAGES). Suggestion: move [specific content] to appendix."
+
+### Step 6.5: Stale File Detection
+
+Check for orphaned section files not referenced by `main.tex`:
+
+```bash
+# Find all .tex files in sections/ and check which are \input'ed by main.tex
+for f in paper/sections/*.tex; do
+    base=$(basename "$f")
+    if ! grep -q "$base" paper/main.tex; then
+        echo "WARNING: $f is not referenced by main.tex — consider removing"
+    fi
+done
+```
+
+This prevents confusion from leftover files when section structure changes (e.g., old `5_conclusion.tex` left behind after restructuring to 7 sections).
+
+### Step 7: Submission Readiness
+
+For conference submission, additional checks:
+
+- [ ] **Anonymous**: no author names, affiliations, or self-citations that reveal identity
+- [ ] **Page limit**: main body within MAX_PAGES (to end of Conclusion)
+- [ ] **Font embedding**: all fonts embedded in PDF
+  ```bash
+  pdffonts main.pdf | grep -v "yes"  # should return nothing (or only header)
+  ```
+- [ ] **No supplementary mixed in**: appendix clearly after `\newpage\appendix`
+- [ ] **File size**: reasonable (< 50MB for most venues, < 10MB preferred)
+- [ ] **No `[VERIFY]` markers**: search the PDF text for leftover markers
+
+### Step 8: Output Summary
+
+```markdown
+## Compilation Report
+
+- **Status**: SUCCESS / FAILED
+- **PDF**: paper/main.pdf
+- **Pages**: X (main body to Conclusion) + Y (references) + Z (appendix)
+- **Within page limit**: YES/NO (MAX_PAGES = N)
+- **Errors fixed**: [list of auto-fixed issues]
+- **Warnings remaining**: [list of non-critical warnings]
+- **Undefined references**: 0
+- **Undefined citations**: 0
+
+### Next Steps
+- [ ] Visual inspection of PDF
+- [ ] Run `/paper-write` to fix any content issues
+- [ ] Submit to [venue] via OpenReview / CMT / HotCRP
+```
+
+## Key Rules
+
+- **Never delete the user's source files** — only modify to fix errors
+- **Keep compile.log** — useful for debugging
+- **Don't suppress warnings** — report them, let the user decide
+- **If LaTeX is not installed**, provide clear installation instructions rather than failing silently
+- **Font embedding is critical** — some venues reject PDFs with non-embedded fonts
+- **Page count = main body to Conclusion** — this is the metric that matters for submission
+
+## Common Venue Requirements
+
+| Venue | Style File | Citation | Page Limit (main body) | Submission |
+|-------|-----------|----------|------------------------|------------|
+| ICLR 2026 | `iclr2026_conference.sty` | `natbib` (`\citep`/`\citet`) | 9 pages (to Conclusion end) | OpenReview |
+| NeurIPS 2025 | `neurips_2025.sty` | `natbib` (`\citep`/`\citet`) | 9 pages (to Conclusion end) | OpenReview |
+| ICML 2025 | `icml2025.sty` | `natbib` (`\citep`/`\citet`) | 8 pages (to Conclusion end) | OpenReview |