Docs & Writing

melodic-software Bundle

Read-only session orientation from durable + off-thread state, synthesize where we stand, what we are doing, and why, from the ledger files, handoff save-points, workflow checklists, running-retro ledgers, open PRs and work-items, and git state, not just the conversation. Complements the built-in /recap (conversation-only, auto-fires) by adding the durable state recap never sees. Use when: 'where were we', 'catch me up', 'orient me', 'get my bearings', 'what's the state', 'brief me', 'situation report', 'where do we stand', 'lay of the land'. Read-only: writes nothing, ends nothing, and does not verify freshness, recover off-thread work, or prescribe the next stage; it points at the sibling that does.

melodic-software Bundle

Capture a baseline or post-change performance snapshot with the HOST QUALIFIED FIRST: repeated no-op spawns characterize the machine's own noise, and a wall-clock claim is REFUSED outright from a host carrying the bimodal contention signature, naming the drift-immune counter it can still report instead. Interleaves before/after arms within one run rather than comparing two passes, since a host that drifts 6x in an hour attributes its own drift to the change. Reports a counter alongside and ranked above any duration. Use when: capturing a before or after snapshot, running the comparison between them, or asking whether this machine can support a timing claim at all: 'capture a baseline', 'take a post snapshot', 'run the A/B', 'can I even measure here'. Runs after /performance:goal; hands off to /performance:verify. Skip when no goal with a computed floor exists yet (run /performance:goal), or when the claim is about code shape rather than runtime (that is /verification:measure metrics).

melodic-software Bundle

Retire finished off-thread work and reconcile this session's task ledger with reality, the prune-and-reconcile counterpart to keep-going's resume. Inventory the off-thread work this session spawned, inspect each item's REAL state, retire the genuinely finished, close the ledger items proven done, and report sibling-session liveness read-only. Auto-settles the provably-finished; GATES any kill of still-running work. Use when: 'reconcile the session', 'retire finished work', 'square up the task ledger', 'is anything still running that should be retired', 'close out finished tasks', 'prune done work', 'reconcile the ledger'. Boundary: 'is it stuck / pick it back up' is /session-flow:keep-going; a read-only 'where do we stand' glance is /session-flow:orient; making git/PR work durable before shutdown is /session-flow:clean-stop.

melodic-software Bundle

Read and report on locally captured Claude Code telemetry, OTEL DuckDB store, collector, optional Aspire dashboard, the per-session hook event log and hook-event JSONL, ccusage, with cross-session trend reports, a per-session report, and store pruning. Use when: 'claude observability', 'OTEL', 'collector', 'token burn rate', 'hook latency', 'cost breakdown', 'how am I doing', 'what did this session do', 'hook event log', 'which hooks fired'; read-only except the explicit clean action.

melodic-software Bundle

Deduplicate repeated markdown content, rule files, skill bodies, ADRs, docs, into a single named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept appears (or is reworded) across files: 'DRY this prose', 'extract a shared rule', 'single source of truth for X', a value-bump diff touching several files. Reports duplication at every multiplicity in rule-of-one / rule-of-two / rule-of-three buckets, offering only non-abstracting remedies below three. Creating a NEW SSOT artifact still refuses below the Rule of Three.

melodic-software Bundle

Lay out which skills fit this moment as a decidable menu, a ranked shortlist per bucket plus the complete remainder by name, so nothing is hidden and the human chooses. Buckets: Now, Next, Skipped upstream (artifact-grounded), Later (the in-domain remainder, named-only), and a rotating Spotlight of three. Never omits an option because it judges the step already done or unnecessary; that judgment becomes an annotation and may affect rank, never presence. Resolves candidates from the full installed catalog rather than the in-context skill listing, which omits every manual-only skill and truncates most descriptions. Use when: 'what should I run next', 'what are my options', 'what am I forgetting', 'which skill fits here', 'what else could I run', 'show me my options', 'what skills apply now'. Writes one small rotation ledger per invocation so the Spotlight advances; otherwise read-only. Not the staged-workflow navigator that routes to exactly one next stage (/session-flow:workflow), not a situation report (/sess

golemcloud Skill

Cutting a new docs version, promoting next to a release, and managing versioned documentation content under docs/src/content/. Use when releasing a Golem version, backporting docs fixes, renaming a docs version, or changing the version selector.

robsonkades Bundle

Evaluating Project Valhalla value-class proposals and Early-Access builds without presenting draft syntax or flattening heuristics as released Java behavior. Use when code or documentation claims value classes remove identity, guarantee flattened storage, eliminate boxing, change object layout, or are available in a particular JDK; and when designing an experiment for a future migration. Does not replace current object-layout measurement (object-layout-and-footprint), escape-analysis diagnosis (escape-analysis-internals), or general JDK upgrade planning (jdk-upgrade-impact).

robsonkades Bundle

Write or review tests for architectural promises: dependency boundaries, transaction atomicity, persistence mappings, stale-write detection, query budgets and API/event compatibility. Use when green tests missed a lost update or N+1, a boundary exists only in documentation, or an integration test may hide the behavior it claims to verify. Does not choose the architecture or governance thresholds (architecture-fitness-functions), replace general unit-test design, or establish production capacity (load-testing).

knuckles-team Skill

Polished verifier skill with drift report and CHECKLIST.md output for spec-kit parity

knuckles-team Skill

Strict Test-Driven Development (TDD) methodology guide using the Red-Green- Refactor cycle. Use when implementing features or fixing bugs with TDD, or when the user mentions TDD, test-first development, or comprehensive test coverage requirements. Do NOT use for pure design discussions, documentation tasks, or research-only work.

knuckles-team Bundle

Review a contract for risk and compliance: parse the document, extract and assess clauses, research legal context, check compliance, and produce a risk report. Use when reviewing contracts or assessing contractual risk.

knuckles-team Skill

Read-only host process inspector for a hot, slow, or swap-thrashing machine. Over SSH via tunnel-manager (or systems-manager) it ranks the worst CPU/RAM offenders, finds zombie/defunct processes and names their non-reaping parent, flags orphaned-to-PID1 runaways (a search or job whose launching session exited and got reparented to init), detects swap exhaustion and which processes hold the most swap, lists uninterruptible D-state processes, and — best effort — maps a culprit PID back to its owning tmux session. Produces a ranked hog report with kill/reap candidates and a load-vs-cores verdict. Use when a host's load is high, a box feels sluggish, or leaked/zombie processes are suspected. Read-only — it NEVER kills, reaps, or tunes anything; pair it with the systems-issue-troubleshooter workflow or host-doctor for gated remediation. Not for disk cleanup (use host-disk-reclaimer) or plain resource sampling (use host-resource-sampler).

knuckles-team Bundle

Interact with Gmail, Google Calendar, Google Chat, Google Docs, Google Drive, Google Sheets, and Google Slides. Use for searching or managing Workspace content, messages, files, events, documents, spreadsheets, or presentations.

knuckles-team Bundle

Ingest market data, backtest a supplied multi-factor strategy with Qlib, and render the per-factor performance breakdown in `backtest_report` as a formatted attribution document. Use when a researcher wants an evidence-linked P&L attribution report; this workflow does not place trades.

knuckles-team Bundle

Ingest reference market data and execute a supplied strategy via paper trading with freqtrade to capture its own fill/slippage report. Use when a researcher wants evidence of execution slippage against reference prices for a candidate strategy; this workflow only paper-trades and never places live orders.

knuckles-team Bundle

Unattended overnight research loop: Generate → Backtest → Debate → Report.

knuckles-team Bundle

Ingest market data, backtest a supplied strategy definition with Qlib, and render the resulting performance metrics as a formatted tearsheet document. Use when a researcher wants a repeatable, generated performance report from a single strategy backtest; this workflow never places or recommends live trades.

knuckles-team Bundle

Outline and draft the talk track, render it as Marp presentation slides, and run a final readiness check. Use when a user has supplied a topic, audience, and voice constraints and wants review-ready slides; this workflow never publishes or presents it.

knuckles-team Bundle

Ingest market data, backtest a supplied regime-classification factor set with Qlib, and render the results as a formatted report. Use when a researcher wants an evidence-linked snapshot of the current market regime; this workflow does not place trades or guarantee regime persistence.

knuckles-team Bundle

Connect to a supplied set of targets, parse their TLS certificates for expiration and grade, and render the results as a formatted sweep report. Use when a fleet operator needs a recurring certificate-expiry report; this workflow is read-only and does not rotate or reissue certificates.

knuckles-team Bundle

Build the pairs-trading portfolio project end-to-end: find two correlated stocks, test for cointegration, trade the z-score of their spread, backtest it leak-free, report full stats, and publish a GitHub repo. The best single learning project in quant finance — teaches hypothesis testing, z-scores, position sizing, and risk management at once.

knuckles-team Bundle

Ingest market data for a supplied existing portfolio's holdings, backtest that portfolio with Qlib, and render the resulting performance metrics as a formatted tearsheet document. Use when a researcher wants a repeatable report for an already-held multi-position portfolio, as distinct from a single strategy definition; this workflow never places or recommends live trades.

knuckles-team Bundle

Fetches a Confluence wiki page, saves it locally as a standard markdown file, and pre-stages the artifact for seamless Knowledge Graph ingestion.

xjli360 Bundle

Triage negative Amazon reviews into policy violations, suspected abuse, and genuine product feedback, then prepare factual official reports and product-remediation actions. Use when the user asks whether a review can be removed, how to report abusive content, or how to respond to a rating decline. Never fabricate evidence, contact reviewers off-platform, or incentivize review changes.

legendtkl Skill

Skill for editing YAML frontmatter in the context of Markdown documents. Use when the user's task is specifically about editing YAML frontmatter.

okhp3 Bundle

OverKill Hill P³ Glee-fully SPA styling. Use when a user wants a Glee-fully application, documentation artifact, presentation, or image brief aligned to the approved Glee-fully profile. Also activate when a target needs retro-bright, warm, emotionally intelligent tooling. This specialization applies the approved local profile and does not substitute OverKill Hill or AskJamie styling.

okhp3 Bundle

Draft a new Discord message, forum post, or thread opener for a named server destination. Use when the user asks to post an announcement, update, question, or discussion opener in Discord. It checks server, channel, and ping context, uses Discord-friendly Markdown when useful, and returns a draft only. Do not use for replies, direct messages, or sending content.

okhp3 Bundle

Draft a Reddit comment or nested reply from supplied submission, thread, and community-rule context. Use when the user wants a grounded contribution to a named Reddit conversation. It returns a draft only and does not comment, vote, report, message moderators, moderate content, or coordinate engagement.

okhp3 Bundle

Draft a TikTok comment or reply from supplied post and conversation context. Use when the user wants a context-aware response under a named TikTok post. It returns reviewable text only and does not post, delete, report, block, follow, message, manage filters, or automate engagement.

okhp3 Bundle

OverKill Hill P³ OverKill Hill SPA styling. Use when a user wants an OverKill Hill application, documentation artifact, presentation, or image brief aligned to the approved OverKill Hill profile. Also activate when a target needs the forge-like technical visual system of the OverKill Hill family. This specialization applies the approved local profile and does not substitute Glee-fully or AskJamie styling.

okhp3 Bundle

Draft an X reply, called a Twitter comment in this family, to a supplied post and conversation. Use when the user wants to reply on X, answer a tweet, join an existing X thread, request feedback, or report public progress. It keeps the parent context and reply visibility in view, then returns a draft only. Do not use for a new standalone post or publication.

okhp3 Bundle

OverKill Hill P³ repository organizer for content-first Git repositories. Use when a local Git repository grew organically from a folder and needs an evidence-based profile, purpose summary, classification, cross-platform naming cleanup, folder design, governance scaffolding, or a safe reorganization plan. Also activate when a repository contains prompts, AI conversations, research, Word documents, spreadsheets, PDFs, images, or mixed knowledge assets rather than a conventional application. This is the authoritative workflow for understanding and organizing an existing repository; use it instead of application-template advice, skill cataloging, or new-repository creation workflows.

okhp3 Bundle

Assemble all validated BP-SKILL process artifacts into a publication-ready bundle with a manifest, approvals record, and completeness check. Use this skill when the user is ready to publish or hand off a complete process documentation set; when they ask to package the process docs, create a handoff bundle, publish the process artifacts, or generate a release package. Requires a passing validation report (Band A or B) before bundling. Produces a MANIFEST.yaml, APPROVALS.yaml, and a ZIP-ready directory structure.

okhp3 Bundle

OverKill Hill P³ repository organizer for content-first Git repositories. Use when a local Git repository grew organically from a folder and needs an evidence-based profile, purpose summary, classification, cross-platform naming cleanup, folder design, governance scaffolding, or a safe reorganization plan. Also activate when a repository contains prompts, AI conversations, research, Word documents, spreadsheets, PDFs, images, or mixed knowledge assets rather than a conventional application. This is the authoritative workflow for understanding and organizing an existing repository; use it instead of application-template advice, skill cataloging, or new-repository creation workflows.

okhp3 Bundle

Extract pasted or uploaded AI chat threads into standalone, actionable Markdown. Use when the user wants to evacuate context from ChatGPT, Claude, Gemini, Perplexity, Microsoft Copilot, Grok, Mistral Vibe, an unknown AI platform, or a mixed transcript; preserve goals, decisions, reasoning, next actions, prompts, code, files, images, citations, canvases, artifacts, diagrams, and provenance; resolve uncertain speaker boundaries; or requests rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catalog depth. Use for complete, partial, flattened, exported, or turn-by-turn human-supplied captures. Do not use for logging into or scraping source services, lossless transcript archival, ordinary short-form summaries, or platform support questions that do not require a durable handoff artifact.