菜单
Opinion tracker for relationship notes. PROACTIVE: When the user confirms a preference ('yes exactly', 'keep doing that'), contradicts one ('no, don't do that', 'stop'), or you observe a recurring behavioral pattern — invoke this to update opinion confidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | opinion |
| description | Opinion tracker for relationship notes. PROACTIVE: When the user confirms a preference ('yes exactly', 'keep doing that'), contradicts one ('no, don't do that', 'stop'), or you observe a recurring behavioral pattern — invoke this to update opinion confidence. |
Tool: tools/opinion.ts
Manage confidence-scored opinions about the user. Opinions are promoted from recurring relationship notes (the W/O/B observations captured at session end). This tool is the fast path to grow opinion confidence — relationship notes feed the slow path (+2% per reflect cycle), while explicit confirmations here jump +10%.
Opinions at ≥85% confidence are automatically injected into every session context.
Proactively call this tool during conversations when:
The user explicitly confirms a preference → --confirmation
The user explicitly contradicts a preference → --contradiction
You observe a recurring behavioral pattern → --supporting
Do NOT call when:
# List all tracked opinions
bun opinion.ts list
# Show details for a specific opinion (fuzzy-matched)
bun opinion.ts show "keywords"
# Add a new opinion (starts at 50%)
bun opinion.ts add "statement" [--category workflow]
# Add evidence to an existing opinion
bun opinion.ts evidence "keywords" --supporting "why" # +2%
bun opinion.ts evidence "keywords" --counter "why" # -5%
bun opinion.ts evidence "keywords" --confirmation "why" # +10%
bun opinion.ts evidence "keywords" --contradiction "why" # -20%
communication | technical | workflow | general
New opinion (add) → 50%
├── supporting evidence → +2% each
├── counter evidence → -5% each
├── explicit confirmation → +10% each
├── explicit contradiction → -20% each
└── at ≥85% → auto-injected into session context
# User says "yes keep it concise, I don't need long explanations"
bun opinion.ts evidence "concise responses" --confirmation "User explicitly said keep it concise"
# User asks for detailed explanation (contradicts concise preference)
bun opinion.ts evidence "concise responses" --contradiction "User requested detailed explanation for this topic"
# You notice user prefers iterative development for the 3rd time
bun opinion.ts evidence "iterative development" --supporting "User again chose incremental approach over big-bang change"
# New pattern: user always checks git status before committing
bun opinion.ts add "User checks git status before every commit" --category workflow
Rewrites text to remove AI slop and make it sound human: eliminates em-dashes and en-dashes, LLM tell-words (delve, leverage, robust, seamless), 'not just X, it's Y' constructions, rule-of-three padding, boilerplate openers/closers, hedging, and decorative emoji, while preserving meaning and voice. Use when asked to humanize text, de-slop, remove AI dashes or em-dashes, strip AI tells, make writing sound human, or clean AI-generated prose.
Author a NEW skill that ships WITH the PAL repo (committed to assets/skills/ and installed for every downstream user). Use only when working inside the portable-agent-layer repo and adding a shared, general-purpose skill. For a user's own private skill, use create-skill instead.
Create a user-scoped subagent for every installed agent (Claude Code, opencode, Cursor, Copilot) from one merged definition, then install and run the doctor on it. Use when the user asks to create a subagent, add a custom agent, delegate a role to a specialized agent, or "make a subagent that…".
Create a new personal skill for this user, scaffolded into their own ~/.pal/skills/ and linked into every installed agent. Use when the user asks to create a skill, add a capability, build a custom command, or "make a skill that…".
Convert markdown files into a styled PDF. Use when creating a PDF from existing markdown files, combining markdown into a report, or converting .md to .pdf.
Project context management. PROACTIVE — use when the user references a project (by name or as "this repo", "current work"), asks to add/update/complete a project, says "store under a named project", "track this", "what am I working on", "my projects", "my priorities". Also triggered by ISC/ISA terminology — ISC stands for Ideal State Criteria, a project's verifiable done-conditions stored as `ISC-N:` lines in the Criteria section of its ISA.md spec. Phrases like "ISC", "open/opening the ISC", "open ISCs" (unfinished criteria), "create/creating a ticket for a project", "new ticket", or "project ticket" all map here: use `list-isc` to read them, `add-isc` to create one, `complete-isc`/`reopen-isc` to change status.