pi-skill-search 0.1.0

package/skills/writer-memory/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: writer-memory
+description: Agentic memory system for writers - track characters, relationships, scenes, and themes
+---
+
+# Writer Memory - Agentic Memory System for Writers
+
+Persistent memory system designed for creative writers, with first-class support for Korean storytelling workflows.
+
+## Overview
+
+Writer Memory maintains context across Claude sessions for fiction writers. It tracks:
+
+- **Characters (캐릭터)**: Emotional arcs (감정궤도), attitudes (태도), dialogue tone (대사톤), speech levels
+- **World (세계관)**: Settings, rules, atmosphere, constraints
+- **Relationships (관계)**: Character dynamics and evolution over time
+- **Scenes (장면)**: Cut composition (컷구성), narration tone, emotional tags
+- **Themes (테마)**: Emotional themes (정서테마), authorial intent
+
+All data persists in `.writer-memory/memory.json` for git-friendly collaboration.
+
+## Commands
+
+| Command | Action |
+|---------|--------|
+| `writer-memory init <project-name>` | Initialize new project memory |
+| `writer-memory status` | Show memory overview (character count, scene count, etc) |
+| `writer-memory char add ` | Add new character |
+| `writer-memory char ` | View character details |
+| `writer-memory char update  <field> <value>` | Update character field |
+| `writer-memory char list` | List all characters |
+| `writer-memory rel add <char1> <char2> <type>` | Add relationship |
+| `writer-memory rel <char1> <char2>` | View relationship |
+| `writer-memory rel update <char1> <char2> <event>` | Add relationship event |
+| `writer-memory scene add <title>` | Add new scene |
+| `writer-memory scene <id>` | View scene details |
+
+## Memory Types
+
+### 캐릭터 메모리 (Character Memory)
+
+Tracks individual character attributes essential for consistent portrayal:
+
+| Field | Korean | Description |
+|-------|--------|-------------|
+| `arc` | 감정궤도 | Emotional journey (e.g., "체념 -> 욕망자각 -> 선택") |
+| `attitude` | 태도 | Current disposition toward life/others |
+| `tone` | 대사톤 | Dialogue style (e.g., "담백", "직설적", "회피적") |
+| `speechLevel` | 말투 레벨 | Formality: 반말, 존댓말, 해체, 혼합 |
+| `keywords` | 핵심 단어 | Characteristic words/phrases they use |
+| `taboo` | 금기어 | Words/phrases they would never say |
+| `emotional_baseline` | 감정 기준선 | Default emotional state |
+| `triggers` | 트리거 | What provokes emotional reactions |
+
+### 세계관 메모리 (World Memory)
+
+Establishes the universe your story inhabits:
+
+| Field | Korean | Description |
+|-------|--------|-------------|
+| `setting` | 배경 | Time, place, social context |
+| `rules` | 규칙 | How the world operates (magic systems, social norms) |
+| `atmosphere` | 분위기 | Overall mood and tone |
+| `constraints` | 제약 | What cannot happen in this world |
+| `history` | 역사 | Relevant backstory |
+
+### 관계 메모리 (Relationship Memory)
+
+Captures the dynamic between characters over time:
+
+| Field | Description |
+|-------|-------------|
+| `type` | Base relationship: romantic, familial, friendship, rivalry, professional |
+| `status` | Current state: budding, stable, strained, broken, healing |
+| `power_dynamic` | Who has the upper hand, if any |
+| `events` | Timeline of relationship-changing moments |
+| `tension` | Current unresolved conflicts |
+| `intimacy_level` | Emotional closeness (1-10) |
+
+**Example:**
+
+

package/skills/writing-plans/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: writing-plans
+description: Use when you have a spec or requirements for a multi-step task, before touching code
+---
+
+# Writing Plans
+
+## Overview
+
+Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
+
+Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
+
+**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."
+
+**Context:** If working in an isolated worktree, it should have been created via the `superpowers:using-git-worktrees` skill at execution time.
+
+**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
+- (User preferences for plan location override this default)
+
+## Scope Check
+
+If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
+
+## File Structure
+
+Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
+
+- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.
+- You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.
+- Files that change together should live together. Split by responsibility, not by technical layer.
+- In existing codebases, follow established patterns. If the codebase uses large files, don't unilaterally restructure - but if a file you're modifying has grown unwieldy, including a split in the plan is reasonable.
+
+This structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.
+
+## Bite-Sized Task Granularity
+
+**Each step is one action (2-5 minutes):**
+- "Write the failing test" - step
+- "Run it to make sure it fails" - step
+- "Implement the minimal code to make the test pass" - step
+- "Run the tests and make sure they pass" - step
+- "Commit" - step
+
+## Plan Document Header
+
+**Every plan MUST start with this header:**
+
+```markdown
+# [Feature Name] Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** [One sentence describing what this builds]
+
+**Architecture:** [2-3 sentences about approach]
+
+**Tech Stack:** [Key technologies/libraries]
+
+---
+```
+
+## Task Structure
+
+````markdown
+### Task N: [Component Name]
+
+**Files:**
+- Create: `exact/path/to/file.py`
+- Modify: `exact/path/to/existing.py:123-145`
+- Test: `tests/exact/path/to/test.py`
+
+- [ ] **Step 1: Write the failing test**
+
+```python
+def test_specific_behavior():
+    result = function(input)
+    assert result == expected
+
+
+## No Placeholders
+
+Every step must contain the actual content an engineer needs. These are **plan failures** — never write them:
+- "TBD", "TODO", "implement later", "fill in details"
+- "Add appropriate error handling" / "add validation" / "handle edge cases"
+- "Write tests for the above" (without actual test code)
+- "Similar to Task N" (repeat the code — the engineer may be reading tasks out of order)
+- Steps that describe what to do without showing how (code blocks required for code steps)
+- References to types, functions, or methods not defined in any task
+
+## Remember
+- Exact file paths always
+- Complete code in every step — if a step changes code, show the code
+- Exact commands with expected output
+- DRY, YAGNI, TDD, frequent commits
+
+## Self-Review
+
+After writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.
+
+**1. Spec coverage:** Skim each section/requirement in the spec. Can you point to a task that implements it? List any gaps.
+
+**2. Placeholder scan:** Search your plan for red flags — any of the patterns from the "No Placeholders" section above. Fix them.
+
+**3. Type consistency:** Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called `clearLayers()` in Task 3 but `clearFullLayers()` in Task 7 is a bug.
+
+If you find issues, fix them inline. No need to re-review — just fix and move on. If you find a spec requirement with no task, add the task.
+
+## Execution Handoff
+
+After saving the plan, offer execution choice:
+
+**"Plan complete and saved to `docs/superpowers/plans/<filename>.md`. Two execution options:**
+
+

package/skills/writing-skills/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: writing-skills
+description: Use when creating new skills, editing existing skills, or verifying skills work before deployment
+---
+
+# Writing Skills
+
+## Overview
+
+**Writing skills IS Test-Driven Development applied to process documentation.**
+
+**Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** 
+
+You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes).
+
+**Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
+
+**REQUIRED BACKGROUND:** You MUST understand superpowers:test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill adapts TDD to documentation.
+
+**Official guidance:** For Anthropic's official skill authoring best practices, see anthropic-best-practices.md. This document provides additional patterns and guidelines that complement the TDD-focused approach in this skill.
+
+## What is a Skill?
+
+A **skill** is a reference guide for proven techniques, patterns, or tools. Skills help future Claude instances find and apply effective approaches.
+
+**Skills are:** Reusable techniques, patterns, tools, reference guides
+
+**Skills are NOT:** Narratives about how you solved a problem once
+
+## TDD Mapping for Skills
+
+| TDD Concept | Skill Creation |
+|-------------|----------------|
+| **Test case** | Pressure scenario with subagent |
+| **Production code** | Skill document (SKILL.md) |
+| **Test fails (RED)** | Agent violates rule without skill (baseline) |
+| **Test passes (GREEN)** | Agent complies with skill present |
+| **Refactor** | Close loopholes while maintaining compliance |
+| **Write test first** | Run baseline scenario BEFORE writing skill |
+| **Watch it fail** | Document exact rationalizations agent uses |
+| **Minimal code** | Write skill addressing those specific violations |
+| **Watch it pass** | Verify agent now complies |
+| **Refactor cycle** | Find new rationalizations → plug → re-verify |
+
+The entire skill creation process follows RED-GREEN-REFACTOR.
+
+## When to Create a Skill
+
+**Create when:**
+- Technique wasn't intuitively obvious to you
+- You'd reference this again across projects
+- Pattern applies broadly (not project-specific)
+- Others would benefit
+
+**Don't create for:**
+- One-off solutions
+- Standard practices well-documented elsewhere
+- Project-specific conventions (put in CLAUDE.md)
+- Mechanical constraints (if it's enforceable with regex/validation, automate it—save documentation for judgment calls)
+
+## Skill Types
+
+### Technique
+Concrete method with steps to follow (condition-based-waiting, root-cause-tracing)
+
+### Pattern
+Way of thinking about problems (flatten-with-flags, test-invariants)
+
+## Directory Structure
+
+
+```
+skills/
+  skill-name/
+    SKILL.md              # Main reference (required)
+    supporting-file.*     # Only if needed
+
+**Flat namespace** - all skills in one searchable namespace
+
+**Separate files for:**
+1. **Heavy reference** (100+ lines) - API docs, comprehensive syntax
+2. **Reusable tools** - Scripts, utilities, templates
+
+## SKILL.md Structure
+
+**Frontmatter (YAML):**
+- Two required fields: `name` and `description` (see [agentskills.io/specification](https://agentskills.io/specification) for all supported fields)
+- Max 1024 characters total
+- `name`: Use letters, numbers, and hyphens only (no parentheses, special chars)
+- `description`: Third-person, describes ONLY when to use (NOT what it does)
+  - Start with "Use when..." to focus on triggering conditions
+  - Include specific symptoms, situations, and contexts
+  - **NEVER summarize the skill's process or workflow** (see CSO section for why)
+  - Keep under 500 characters if possible
+
+```markdown
+---
+name: Skill-Name-With-Hyphens
+description: Use when [specific triggering conditions and symptoms]
+---
+
+# Skill Name
+
+## Overview
+What is this? Core principle in 1-2 sentences.
+
+## When to Use
+[Small inline flowchart IF decision non-obvious]
+
+Bullet list with SYMPTOMS and use cases
+When NOT to use
+
+## Core Pattern (for techniques/patterns)
+
+

package/skills/xgboost/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: xgboost
+description: Gradient boosted decision trees for machine learning. Use when training classification or regression models on tabular data, feature importance analysis, or hyperparameter tuning. Trigger on imports of xgboost, XGBClassifier, XGBRegressor, or mentions of gradient boosting, decision tree, ensemble, tabular ML, scikit, sklearn.
+---
+# xgboost
+
+Use this skill for gradient boosting on tabular data.
+
+## Core patterns
+
+- **Train**: `XGBClassifier(n_estimators=500, max_depth=6, learning_rate=0.1).fit(X_train, y_train)`.
+- **DMatrix**: `DMatrix(data, label)` for optimized data loading.
+- **CV**: `xgb.cv(params, dtrain, num_boost_round=1000, nfold=5, early_stopping_rounds=50)`.
+- **Feature importance**: `model.feature_importances_` or `xgb.plot_importance(model)`.
+- **Save/Load**: `model.save_model('model.json')` / `XGBClassifier().load_model('model.json')`.
+
+## Rules
+
+- Always use `early_stopping_rounds` with eval set to prevent overfitting.
+- Scale `scale_pos_weight` for imbalanced datasets: `sum(negative) / sum(positive)`.
+- Use `n_estimators` + `early_stopping` instead of guessing optimal round count.
+
+## Anti-patterns
+
+- Don't use default hyperparameters for production — always tune.
+- Don't ignore categorical encoding — XGBoost needs numeric input.
+- Don't interpret feature importance as causal relationship.
+
+

package/skills/xgboost-ts/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: xgboost-ts
+description: Time series forecasting with machine learning. Use when predicting future values from temporal data, ARIMA alternatives, seasonality decomposition, or demand forecasting. Trigger on imports of prophet, darts, or mentions of time series, forecasting, prediction, seasonal, trend, ARIMA, LSTM.
+---
+# xgboost-ts
+
+Use this skill for time series forecasting with ML approaches.
+
+## Core patterns
+
+- **Features**: Create lag features (`df['lag_1'] = df['value'].shift(1)`), rolling stats, Fourier terms.
+- **Train**: Split by time (not random) — use `train_test_split(shuffle=False)`.
+- **Prophet**: `Prophet(yearly_seasonality=True).fit(df)` for automatic decomposition.
+- **Evaluate**: MAE, MAPE, MASE on holdout — never on training data.
+
+## Rules
+
+- Always use time-based split, not random — data leakage otherwise.
+- Stationarity: difference the series if ADF test shows unit root.
+- Cross-validation: use `TimeSeriesSplit` with expanding window.
+
+## Anti-patterns
+
+- Don't use future data in lag features — check for lookahead bias.
+- Don't forecast too far ahead — uncertainty grows quadratically.
+- Don't ignore seasonality — decompose before modeling.
+
+

package/skills/xlsx/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: xlsx
+description: "Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved."
+---
+
+# Requirements for Outputs
+
+## All Excel files
+
+### Professional Font
+- Use a consistent, professional font (e.g., Arial, Times New Roman) for all deliverables unless otherwise instructed by the user
+
+### Zero Formula Errors
+- Every Excel model MUST be delivered with ZERO formula errors (#REF!, #DIV/0!, #VALUE!, #N/A, #NAME?)
+
+### Preserve Existing Templates (when updating templates)
+- Study and EXACTLY match existing format, style, and conventions when modifying files
+- Never impose standardized formatting on files with established patterns
+- Existing template conventions ALWAYS override these guidelines
+
+## Financial models
+
+### Color Coding Standards
+Unless otherwise stated by the user or existing template
+
+#### Industry-Standard Color Conventions
+- **Blue text (RGB: 0,0,255)**: Hardcoded inputs, and numbers users will change for scenarios
+- **Black text (RGB: 0,0,0)**: ALL formulas and calculations
+- **Green text (RGB: 0,128,0)**: Links pulling from other worksheets within same workbook
+- **Red text (RGB: 255,0,0)**: External links to other files
+- **Yellow background (RGB: 255,255,0)**: Key assumptions needing attention or cells that need to be updated
+
+### Formula Construction Rules
+
+#### Assumptions Placement
+- Place ALL assumptions (growth rates, margins, multiples, etc.) in separate assumption cells
+- Use cell references instead of hardcoded values in formulas
+- Example: Use =B5*(1+$B$6) instead of =B5*1.05
+
+#### Formula Error Prevention
+- Verify all cell references are correct
+- Check for off-by-one errors in ranges
+- Ensure consistent formulas across all projection periods
+- Test with edge cases (zero values, negative numbers)
+- Verify no unintended circular references
+
+#### Documentation Requirements for Hardcodes
+
+# XLSX creation, editing, and analysis
+
+## Overview
+
+A user may ask you to create, edit, or analyze the contents of an .xlsx file. You have different tools and workflows available for different tasks.
+
+## Important Requirements
+
+**LibreOffice Required for Formula Recalculation**: You can assume LibreOffice is installed for recalculating formula values using the `scripts/recalc.py` script. The script automatically configures LibreOffice on first run, including in sandboxed environments where Unix sockets are restricted (handled by `scripts/office/soffice.py`)
+
+## Reading and analyzing data
+
+### Data analysis with pandas
+For data analysis, visualization, and basic operations, use **pandas** which provides powerful data manipulation capabilities:
+
+```python
+import pandas as pd
+
+# Read Excel
+df = pd.read_excel('file.xlsx')  # Default: first sheet
+all_sheets = pd.read_excel('file.xlsx', sheet_name=None)  # All sheets as dict
+
+# Analyze
+df.head()      # Preview data
+df.info()      # Column info
+df.describe()  # Statistics
+
+# Write Excel
+df.to_excel('output.xlsx', index=False)
+```
+
+## Excel File Workflows
+
+## CRITICAL: Use Formulas, Not Hardcoded Values
+
+**Always use Excel formulas instead of calculating values in Python and hardcoding them.** This ensures the spreadsheet remains dynamic and updateable.
+
+### ❌ WRONG - Hardcoding Calculated Values
+```python
+# Bad: Calculating in Python and hardcoding result
+total = df['Sales'].sum()
+sheet['B10'] = total  # Hardcodes 5000
+
+# Bad: Computing growth rate in Python
+growth = (df.iloc[-1]['Revenue'] - df.iloc[0]['Revenue']) / df.iloc[0]['Revenue']
+sheet['C5'] = growth  # Hardcodes 0.15
+
+# Bad: Python calculation for average
+avg = sum(values) / len(values)
+sheet['D20'] = avg  # Hardcodes 42.5
+```
+
+### ✅ CORRECT - Using Excel Formulas
+```python
+# Good: Let Excel calculate the sum
+sheet['B10'] = '=SUM(B2:B9)'
+
+# Good: Growth rate as Excel formula
+sheet['C5'] = '=(C4-C2)/C2'
+
+# Good: Average using Excel function
+sheet['D20'] = '=AVERAGE(D2:D19)'
+```

package/skills/zarr-python/SKILL.md

@@ -0,0 +1,101 @@
+---
+name: zarr-python
+description: Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
+---
+
+# Zarr Python
+
+## Overview
+
+Zarr is a Python library for storing large N-dimensional arrays with chunking and compression. Apply this skill for efficient parallel I/O, cloud-native workflows, and seamless integration with NumPy, Dask, and Xarray.
+
+## Quick Start
+
+### Basic Array Creation
+
+```python
+import zarr
+import numpy as np
+
+# Create a 2D array with chunking and compression
+z = zarr.create_array(
+    store="data/my_array.zarr",
+    shape=(10000, 10000),
+    chunks=(1000, 1000),
+    dtype="f4"
+)
+
+# Write data using NumPy-style indexing
+z[:, :] = np.random.random((10000, 10000))
+
+# Read data
+data = z[0:100, 0:100]  # Returns NumPy array
+```
+
+## Core Operations
+
+### Creating Arrays
+
+Zarr provides multiple convenience functions for array creation:
+
+```python
+# Create empty array
+z = zarr.zeros(shape=(10000, 10000), chunks=(1000, 1000), dtype='f4',
+               store='data.zarr')
+
+# Create filled arrays
+z = zarr.ones((5000, 5000), chunks=(500, 500))
+z = zarr.full((1000, 1000), fill_value=42, chunks=(100, 100))
+
+# Create from existing data
+data = np.arange(10000).reshape(100, 100)
+z = zarr.array(data, chunks=(10, 10), store='data.zarr')
+
+# Create like another array
+z2 = zarr.zeros_like(z)  # Matches shape, chunks, dtype of z
+```
+
+### Opening Existing Arrays
+
+```python
+# Open array (read/write mode by default)
+z = zarr.open_array('data.zarr', mode='r+')
+
+# Read-only mode
+z = zarr.open_array('data.zarr', mode='r')
+
+# The open() function auto-detects arrays vs groups
+z = zarr.open('data.zarr')  # Returns Array or Group
+```
+
+### Reading and Writing Data
+
+Zarr arrays support NumPy-like indexing:
+
+```python
+# Write entire array
+z[:] = 42
+
+# Write slices
+z[0, :] = np.arange(100)
+z[10:20, 50:60] = np.random.random((10, 10))
+
+# Read data (returns NumPy array)
+data = z[0:100, 0:100]
+row = z[5, :]
+
+# Advanced indexing
+z.vindex[[0, 5, 10], [2, 8, 15]]  # Coordinate indexing
+z.oindex[0:10, [5, 10, 15]]       # Orthogonal indexing
+z.blocks[0, 0]                     # Block/chunk indexing
+```
+
+### Resizing and Appending
+
+```python
+# Resize array
+z.resize(15000, 15000)  # Expands or shrinks dimensions
+
+# Append data along an axis
+z.append(np.random.random((1000, 10000)), axis=0)  # Adds rows
+```