opencode-skills-collection 4.0.1 → 4.0.2

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-07-15T01:13:33.382Z",
+  "updatedAt": "2026-07-16T01:22:28.705Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -104,6 +104,7 @@
     "antigravity-design-expert",
     "antigravity-skill-orchestrator",
     "antigravity-workflows",
+    "anywrite",
     "aomi-transact",
     "api-analyzer",
     "api-and-interface-design",
@@ -676,6 +677,7 @@
     "distribute-skill-to-all-agents",
     "distributed-debugging-debug-trace",
     "distributed-tracing",
+    "ditto",
     "django-access-review",
     "django-perf-review",
     "django-pro",
@@ -1308,6 +1310,7 @@
     "openapi-spec-generation",
     "openapi-spec-generator",
     "openclaw-github-repo-commander",
+    "optim-agent",
     "options-flow-analyzer",
     "oral-health-analyzer",
     "orchestrate-batch-refactor",
@@ -1663,6 +1666,7 @@
     "sred-project-organizer",
     "sred-work-summary",
     "ssh-penetration-testing",
+    "sshepherd",
     "stability-ai",
     "startup-analyst",
     "startup-business-analyst-business-case",

package/bundled-skills/anywrite/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: anywrite
+description: "Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed."
+category: productivity
+risk: critical
+source: community
+source_repo: Antheurus/anywrite
+source_type: community
+date_added: "2026-07-15"
+author: Antheurus
+tags: [anytype, cli, pkm, notes, api-integration, productivity, knowledge-management]
+tools: [claude, cursor, gemini, codex]
+license: "MIT"
+license_source: "https://github.com/Antheurus/anywrite/blob/main/LICENSE"
+---
+
+# anywrite
+
+## Overview
+
+`anywrite` is a single compiled Bun/TypeScript CLI for the [Anytype](https://anytype.io) desktop app's local HTTP API — **all 52 endpoints** across spaces, objects, properties, tags, types, templates, lists, chat, files, members, search, and auth — as one binary with zero runtime dependencies. It exists as a low-context alternative to Anytype's official MCP server: rather than exposing 52 always-loaded tools to every agent session, `anywrite` is a normal CLI wired as a skill that costs zero context until it's actually invoked, and is equally usable from a terminal or any script.
+
+## When to Use This Skill
+
+- Use when the user mentions Anytype or asks to create, update, search, or organize notes, tasks, or PKM objects.
+- Use when working with Anytype spaces, properties, tags, types, templates, or lists (sets and collections).
+- Use when the user asks to upload files to a space, chat inside a space, or read/write structured objects programmatically.
+
+## How It Works
+
+### Step 1: Ensure Anytype desktop is running and authenticated
+
+The Anytype desktop app must be running locally (default `http://localhost:31009`). Authenticate once:
+
+```bash
+./dist/anywrite auth --status        # shows configured yes/no and where the key came from
+./dist/anywrite auth                 # challenge flow — a 4-digit code appears in the app
+./dist/anywrite auth --code 1234     # non-interactive form of the same exchange
+```
+
+The key is written to `~/.anywrite/config.json` and is never printed by any command.
+
+### Step 2: Invoke a resource + action
+
+```
+anywrite <resource> <action> [positionals] [--flag value]
+```
+
+Resources: `spaces`, `objects`, `properties`, `tags`, `types`, `templates`, `lists`, `files`, `members`, `search`, `chat`, `auth`. Output is JSON by default; add `--pretty` for a human view, `--json` as an escape hatch for anything the typed flags don't model yet. `space`/`type`/`property` positionals accept a name or an id — names are resolved to ids automatically.
+
+## Examples
+
+### Example 1: Create and update an object
+
+```bash
+./dist/anywrite objects create <space> --type task --name "Buy milk"
+./dist/anywrite objects update <space> <object_id> --status "Done"
+```
+
+### Example 2: Search and upload a file
+
+```bash
+./dist/anywrite search global --query "task" --types task
+./dist/anywrite files upload <space> --file ./image.png
+```
+
+### Example 3: Read chat messages
+
+```bash
+./dist/anywrite chat messages <space> <chat_id> --all
+```
+
+## Best Practices
+
+- ✅ Pass names for `space`/`type`/`property` and let the CLI resolve them to ids.
+- ✅ Use default JSON output for scripting and `--pretty` for human review.
+- ✅ Reach for `--json` when a brand-new API field isn't yet covered by a typed flag.
+- ❌ Don't set an empty-string emoji `--icon`; omit the flag entirely instead.
+- ❌ Don't expect `lists add`/`remove` to work on sets — they only apply to collections.
+
+## Limitations
+
+- This skill does not replace environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
+- Bounded by the Anytype local API itself: no block-level editing (body is whole-markdown replace only), no member invite/role management, no template create/update/delete, no space deletion.
+- The object body field is named `--body` on create but `--markdown` on update.
+
+## Security & Safety Notes
+
+- The API key is stored locally in `~/.anywrite/config.json` and is never printed by any command, including `auth --status`.
+- Config precedence at runtime: `ANYTYPE_API_KEY` env var, then `~/.anywrite/config.json`, then a read-only fallback to an existing `~/.anytype-cli/config.yaml`.
+- All operations target a locally-running Anytype desktop instance; no data is sent to third-party servers.
+- Delete is a soft archive everywhere and is idempotent — a repeated delete stays `200`, never `410`.
+
+## Common Pitfalls
+
+- **Problem:** `lists add`/`remove` silently does nothing on a set.
+  **Solution:** These only work on collections, not sets.
+- **Problem:** Re-uploading an identical file returns an existing object id instead of a new one.
+  **Solution:** This is intentional — file upload dedupes by content hash.
+- **Problem:** Chat messages don't paginate like everything else.
+  **Solution:** Chat paginates by cursor; every other resource paginates by offset.
+
+## Related Skills
+
+- `@docx` - When the deliverable is a Word document rather than an Anytype object.

package/bundled-skills/ditto/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: ditto
+description: "Use when a user asks to mine or update a private, evidence-backed work profile from local Claude Code, Codex, Copilot CLI, or OpenCode sessions."
+category: agent-behavior
+risk: critical
+source: community
+source_repo: ohad6k/ditto
+source_type: community
+date_added: "2026-07-14"
+author: ohad6k
+tags: [personalization, context-engineering, session-mining, agent-memory]
+tools: [claude, cursor, gemini, codex-cli]
+license: "MIT"
+license_source: "https://github.com/ohad6k/ditto/blob/v0.3.6/LICENSE"
+---
+
+# Ditto
+
+## Overview
+
+Ditto mines only the user's words from real local coding-agent session logs and
+turns repeated, supported patterns into private work, design, and writing
+profiles. It keeps dated session receipts, rejects authored rules and memory as
+source evidence, and requires approval before model-backed mining begins.
+
+This standalone skill routes a compatible, already-installed Ditto runtime.
+Native namespaced routing is available through the upstream Ditto plugin.
+
+## When to Use This Skill
+
+- Use when the user explicitly asks to set up, run, update, re-mine, or deepen Ditto.
+- Use when the user wants an agent profile derived from real coding-session history rather than a questionnaire or rules file.
+- Use when native `ditto:mine` is unavailable and the user already has a compatible Ditto runtime installed.
+
+Do not trigger this skill merely because personalization might be useful. Mining
+requires an explicit user request.
+
+## How It Works
+
+### 1. Resolve an installed runtime
+
+Ask the user for the path to an existing, trusted Ditto runtime, or use the
+native upstream plugin when it is already installed. Retain the exact Python 3
+executable path as `PYTHON3`, the runtime path as `DITTO_PY`, and its matching
+`MINING_PROMPT.md` path. Confirm the installed version and source before use.
+
+Do not download or install executable code as part of this skill. If Ditto is
+not installed, stop and direct the user to the upstream installation guidance;
+installation is a separate, explicit decision.
+
+### 2. Show the read-only mining plan
+
+Mine only real user-authored sessions. Never synthesize a profile from
+`AGENTS.md`, `CLAUDE.md`, memory files, rules files, or a typed self-description.
+
+Run the full-history quality-default preflight:
+
+```bash
+"$PYTHON3" "$DITTO_PY" plugin preflight
+```
+
+Show the user the valid session count, post-dedupe source tokens, selected source
+tokens, cache hits, planned worker calls, and planned reducer calls. Wait for
+explicit approval of this displayed plan before any model-backed work.
+
+If the user explicitly asks for a quick preview, add `--preview` and say exactly:
+
+> Quick preview creates a starter profile from selected history, not the full profile.
+
+Never present preview as the default or as equivalent to the full-history result.
+
+### 3. Prepare the approved run
+
+Retain the displayed `approval_hash`, then prepare with the exact approved mode.
+For the full-history plan, run:
+
+```bash
+"$PYTHON3" "$DITTO_PY" plugin prepare --approved-plan-hash HASH
+```
+
+For an approved quick-preview plan, preserve preview mode explicitly:
+
+```bash
+"$PYTHON3" "$DITTO_PY" plugin prepare --preview --approved-plan-hash HASH
+```
+
+If the hash changes, show the new plan and obtain approval again. Retain the
+returned `run_id`, assigned segment and report paths, and `pack_path`.
+
+### 4. Mine and validate evidence
+
+For every uncached selected segment, run one worker over only that segment and
+the per-segment contract in the resolved `MINING_PROMPT.md`. Cache each JSON
+report with `plugin cache-report` and stop on rejection.
+
+Run one strongest-available reducer over only the validated reports and reducer
+contract. Write the complete pack to `pack_path`, validate it, and activate only
+the validated pack with `plugin activate`.
+
+### 5. Verify and report
+
+Run `plugin status`, render the profile card, and report:
+
+- active version and core profile path
+- active and inactive domains
+- selected source tokens and actual worker/reducer passes
+- cache reuse
+- card path
+- any exact targeted-deepen instruction
+
+If the current host already has the native Ditto plugin, do not create a
+competing direct profile installation.
+
+## Examples
+
+### Full-history setup
+
+```text
+User: run ditto on my coding history
+Agent: resolves the pinned runtime, shows the read-only full-history plan, and
+waits for explicit cost approval before starting any mining workers.
+```
+
+### Explicit quick preview
+
+```text
+User: give me a cheap ditto preview first
+Agent: runs preflight with --preview, labels it as a starter profile, and waits
+for approval of the displayed preview plan.
+```
+
+## Best Practices
+
+- Keep raw sessions, caches, receipts, and generated profiles private by default.
+- Report exact observed counts and paths; never estimate provider billing or coverage.
+- Preserve the approval hash and mode through the complete run.
+- Stop on validation failure instead of activating a partial profile.
+- Share the card or a short trait, not the full private profile or receipt appendix.
+
+## Limitations
+
+- Ditto models working behavior; it does not make the underlying model smarter.
+- Sparse or repetitive histories can leave design or writing domains inactive.
+- Provider system prompts, tool traffic, and billing overhead are outside Ditto's exact token accounting.
+- Quick preview has lower recall than the full-history quality default.
+- Automatic work, design, and writing routing requires the upstream native plugin.
+
+## Security & Safety Notes
+
+- This skill does not download executable code; it requires an existing trusted Ditto installation.
+- Extraction, redaction, caches, and generated profiles stay local. Selected redacted text is processed by the model provider the user chooses.
+- Redaction is best-effort. Tell the user to inspect private output before sharing it.
+- Never upload session logs or full profiles to a third party without explicit user approval.
+- Installation itself schedules no mining model calls; every prepared mining mode still requires approval of its displayed plan.
+
+## Common Pitfalls
+
+- **Problem:** No eligible sessions are found.
+
+  **Solution:** Report the supported source locations that were checked and ask whether the user has retained or exported session history.
+
+- **Problem:** The approval hash changed.
+
+  **Solution:** Do not reuse the old approval. Show the updated plan and obtain approval again.
+
+- **Problem:** A cached or reduced report fails validation.
+
+  **Solution:** Stop, preserve the failure evidence, and never activate the incomplete pack.
+
+## Related Skills
+
+- `@agenttrace-session-audit` - Use for cost, latency, failure, and health analysis of coding-agent sessions.
+- `@agent-memory` - Use for explicit persistent knowledge storage rather than evidence-based profile mining.

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,958+ skills."
+description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,962+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,958+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,962+ skills
 
 This guide shows how to integrate the `agentic-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
 
@@ -23,7 +23,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With 1,958+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,962+ skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -21,7 +21,7 @@ This example shows one way to integrate **agentic-awesome-skills** with a Jetski
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,958+ skills installed.
+This pattern avoids context overflow when you have 1,962+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
 
 Preferred positioning:
 
-> Installable GitHub library of 1,958+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,962+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
 
 Key framing:
 
@@ -20,7 +20,7 @@ Key framing:
 
 Preferred description:
 
-> Installable GitHub library of 1,958+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
+> Installable GitHub library of 1,962+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
 
 Preferred homepage:
 
@@ -28,7 +28,7 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,958+ Agentic Skills`;
+- use a clean preview image that says `1,962+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,958+ skills from the skills directory
+- All 1,962+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/users/bundles.md

@@ -1060,4 +1060,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: June 2026 | Total Skills: 1,958+ | Total Bundles: 58_
+_Last updated: June 2026 | Total Skills: 1,962+ | Total Bundles: 58_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
 
 ## Why use this repo for Claude Code
 
-- It includes 1,958+ skills instead of a narrow single-domain starter pack.
+- It includes 1,962+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,958+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,962+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/getting-started.md

@@ -1,4 +1,4 @@
-# Getting Started with Agentic Awesome Skills (V14.4.0)
+# Getting Started with Agentic Awesome Skills (V14.5.0)
 
 **New here? This guide will help you supercharge your AI Agent in 5 minutes.**
 

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,958+ specialized areas
+- **Domain expertise** across 1,962+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture

package/bundled-skills/docs/users/usage.md

@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
 
 When you ran `npx agentic-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,958+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 1,962+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
 ✅ **Made them available** to your AI assistant
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
 
 **Analogy:**
 
-- You installed a toolbox with 1,958+ tools (✅ done)
+- You installed a toolbox with 1,962+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
 
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Step 5: Picking Your First Skills (Practical Advice)
 
-Don't try to use all 1,958+ skills at once. Here's a sensible approach:
+Don't try to use all 1,962+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,958+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,962+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -34,7 +34,7 @@ agentic-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,958+ skills live here
+├── 📁 skills/                          ← 1,962+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ agentic-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,958+ total)
+│   └── ... (1,962+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ agentic-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,958+ SKILLS          │
+                    │  1,962+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,958+ total)                │
+│   └── ... (1,962+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/optim-agent/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: optim-agent
+description: "Guide agent-driven parameter optimization for configurable systems with measurable objectives. Use for HPO, inference tuning, simulations, or RL/control experiments."
+category: data
+risk: safe
+source: community
+source_repo: Optim-Agent/optim-agent
+source_type: community
+date_added: "2026-07-15"
+author: Optim-Agent
+tags: [optimization, hyperparameter-optimization, experiments, tuning]
+tools: [claude, cursor, gemini, codex]
+license: MIT
+license_source: "https://github.com/Optim-Agent/optim-agent/blob/main/LICENSE"
+---
+
+# Optim Agent
+
+## Overview
+
+Use this skill to optimize configurable systems against a measurable scalar objective. It helps an agent turn vague tuning requests into bounded experiments with a defined search space, budget, baseline, and evidence-backed recommendation.
+
+## When to Use This Skill
+
+- Use when tuning hyperparameters, prompts, inference settings, simulation parameters, quantitative strategies, or RL/control policies.
+- Use when the objective can be measured as a scalar score, loss, accuracy, cost, latency, reward, or risk-adjusted metric.
+- Use when the user needs a small-budget optimization loop with trial history, comparisons, and stop criteria.
+
+## Do not use this skill when
+
+- The objective is purely subjective and cannot be scored consistently.
+- The user has not provided permission to run experiments or consume compute/API budget.
+- The task is a one-shot implementation, debugging, or code review request with no configurable search space.
+
+## Instructions
+
+1. Define the optimization target in one sentence: maximize or minimize one scalar metric.
+2. List the tunable parameters, valid ranges, types, defaults, and any forbidden combinations.
+3. Establish at least one baseline before proposing agent-guided trials.
+4. Set the budget up front: number of trials, time, compute, money, or dataset subsample.
+5. Run or request trials one at a time unless the user explicitly approves parallel execution.
+6. Record every trial with parameters, metric value, notes, and failure status.
+7. Compare the best result against the baseline and a simple search strategy when possible.
+8. Stop when the budget is exhausted, the improvement plateaus, or the next trial cannot be justified from evidence.
+9. Report the recommended configuration, measured gain, tradeoffs, and any validation still needed before production use.
+
+## Examples
+
+### Example 1: Hyperparameter optimization
+
+Tune learning rate, regularization, and tree depth for a credit-default model. Track validation AUC for each trial, compare against the default configuration, and recommend the best setting only if it improves the baseline under the agreed trial budget.
+
+### Example 2: Inference tuning
+
+Tune retrieval depth, temperature, and reranker threshold for a RAG workflow. Optimize answer quality under a latency or cost ceiling, then report the best configuration with quality, latency, and cost tradeoffs.
+
+### Example 3: Simulation or control
+
+Tune controller gains or environment parameters for a simulator. Optimize reward or error while logging failed trials separately so unstable configurations do not bias the recommendation.
+
+## Best Practices
+
+- Keep the first run small; expand only after the loop produces useful signal.
+- Prefer parameters with clear operational meaning over arbitrary knobs.
+- Treat failed trials as data and record why they failed.
+- Validate the final configuration on held-out data, a fresh seed, or a separate scenario before calling it robust.
+- Ask before running expensive, long, or externally billed experiments.
+
+## Limitations
+
+- This skill does not guarantee a global optimum.
+- Results depend on objective quality, noise, search-space design, and experiment reproducibility.
+- Use domain review before applying tuned configurations to production, financial, safety-critical, or user-impacting systems.
+
+## Additional Resources
+
+- [Optim-Agent repository](https://github.com/Optim-Agent/optim-agent)
+- [Optim-Agent documentation](https://optim-agent.github.io/optim-agent/)

package/bundled-skills/sshepherd/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: sshepherd
+description: "Zero-knowledge SSH ops CLI — server health checks, docker/systemd control, log tailing, Postgres introspection, and declarative deploys, without ever exposing credentials to the agent."
+category: devops
+risk: critical
+source: community
+source_repo: Antheurus/sshepherd
+source_type: community
+date_added: "2026-07-15"
+author: Antheurus
+tags: [ssh, devops, cli, server-ops, postgres, deploy, zero-knowledge]
+tools: [claude, cursor, gemini, codex]
+license: "MIT"
+license_source: "https://github.com/Antheurus/sshepherd/blob/main/LICENSE"
+---
+
+# sshepherd
+
+## Overview
+
+`sshepherd` is a compiled Bun/TypeScript CLI that lets an agent operate a real remote server over SSH — health checks, docker/systemd service control, log tailing, config file edits, read-only Postgres introspection, and declarative deploys — without ever seeing a password, private key, hostname, username, or port. Every operation shells out to the system `ssh` binary through a single transport path and returns the same typed `Envelope<T>` (`ok`, `alias`, `data`, `error`), never a raw terminal dump. The agent passes only a *name* — an ssh alias, a Postgres target, or a deploy recipe — that resolves entirely outside the process.
+
+## When to Use This Skill
+
+- Use when you need to check a remote server's health (disk, memory, CPU, ports, OOM history) without handing the agent SSH credentials.
+- Use when working with remote docker or systemd services — listing, inspecting, or restarting them — or tailing their logs.
+- Use when the user asks to read or edit a remote config file, run a declarative deploy from a named recipe, introspect a remote Postgres database read-only, or audit SSH/security posture on a box.
+
+## How It Works
+
+### Step 1: Declare targets once, outside any prompt
+
+Every connection detail is declared ahead of time and never appears on the command line: ssh aliases in `~/.ssh/config`, Postgres targets in `~/.config/sshepherd/targets.toml`, deploy recipes in recipe TOML files. OpenSSH resolves the real `HostName`/`User`/`Port`/`IdentityFile` internally.
+
+### Step 2: Invoke a group + action by name
+
+```
+sshepherd <group> <action> [positionals...] [--flag value]
+```
+
+Nine command groups — `hosts`, `check`, `logs`, `services`, `deploy`, `config`, `db`, `files`, `security` — 52 ops total. Output is JSON to stdout by default; add `--pretty` for a human-readable table/key-value view. The response only ever echoes back the `alias` it was given — there is no host/user/port/ip field anywhere in the response type, structurally.
+
+### Step 3: Discover the command surface
+
+```bash
+./dist/sshepherd --help                 # list groups
+./dist/sshepherd check --help           # list actions + flags for one group
+```
+
+## Examples
+
+### Example 1: Server health overview
+
+```bash
+./dist/sshepherd check overview lms-server
+```
+
+Returns a JSON envelope with disk, memory, CPU, listening ports, and OOM history for the host behind the `lms-server` alias — the agent never learns the host's address.
+
+### Example 2: Restart a docker service and tail its logs
+
+```bash
+./dist/sshepherd services restart lms-server --name api
+./dist/sshepherd logs tail lms-server --name api --lines 100
+```
+
+### Example 3: Read-only Postgres introspection
+
+```bash
+./dist/sshepherd db tables prod
+```
+
+`prod` is a pg-target name that resolves to *how* to reach `psql` on a host — never a database password. `psql` runs inside the target container, authenticated by peer/trust/`.pgpass` already on the remote.
+
+## Best Practices
+
+- ✅ Declare every alias/target/recipe ahead of time in `~/.ssh/config` / `targets.toml` / recipe TOML — never inline connection details.
+- ✅ Pass only names (alias, pg-target, recipe) to the CLI; let OpenSSH own authentication.
+- ✅ Use `--pretty` for human review and default JSON output for machine parsing.
+- ❌ Don't try to inject a hostname, user, port, or password into a command — the CLI has no field for them.
+- ❌ Don't reach for the `ssh2` npm library or hand-rolled SSH; the whole point is delegating to the trusted system `ssh` binary.
+
+## Limitations
+
+- This skill does not replace environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
+- Requires the system OpenSSH client and pre-declared aliases/targets/recipes; it cannot connect to a host that has not been configured outside the agent.
+- Postgres access is read-only introspection by design.
+
+## Security & Safety Notes
+
+- **Zero-knowledge credential model:** the agent never sees a password, private key, hostname, username, or port. It only ever passes an ssh alias, a pg-target name, or a recipe name; the real connection tuple is resolved by OpenSSH outside the process, and every response echoes back only the alias.
+- **Never reads private key material.** Authentication happens entirely inside OpenSSH's own trusted code path.
+- **Confirmation gate on mutations:** destructive/mutating actions (service restart, config write, deploy) require an explicit `--yes` confirm flag.
+- **Human-only credential entry:** the separate `setup ssh-alias install` action opens a one-shot local browser form that only a human can type a password into — the agent can trigger and wait on it but never sees, logs, or relays the password.
+- Environment expectation: run against hosts you are authorized to operate.
+
+## Common Pitfalls
+
+- **Problem:** Trying to pass a hostname or password directly to a command.
+  **Solution:** Register the target first (`setup ssh-alias register` / `setup db-target`), then reference it only by name.
+- **Problem:** A mutating action returns without doing anything.
+  **Solution:** Add the `--yes` confirm flag — mutations are gated by design.
+
+## Related Skills
+
+- `@devops-automation` - When you need broader CI/CD or infrastructure-as-code automation beyond SSH ops.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "4.0.1",
+  "version": "4.0.2",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -46,6 +46,6 @@
     "@types/bun": "*",
     "@types/node": "^26.0.0",
     "@types/strip-json-comments": "^3.0.0",
-    "typescript": "^6.0.2"
+    "typescript": "^7.0.2"
   }
 }

package/skills_index.json

@@ -2388,6 +2388,41 @@
       "reasons": []
     }
   },
+  {
+    "id": "anywrite",
+    "path": "skills/anywrite",
+    "category": "productivity",
+    "name": "anywrite",
+    "description": "Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.",
+    "risk": "critical",
+    "source": "community",
+    "date_added": "2026-07-15",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "community",
+    "source_repo": "Antheurus/anywrite",
+    "license": "MIT",
+    "license_source": "https://github.com/Antheurus/anywrite/blob/main/LICENSE",
+    "tags": [
+      "anytype",
+      "cli",
+      "pkm",
+      "notes",
+      "api-integration",
+      "productivity",
+      "knowledge-management"
+    ]
+  },
   {
     "id": "aomi-transact",
     "path": "skills/aomi-transact",
@@ -15445,6 +15480,38 @@
       "reasons": []
     }
   },
+  {
+    "id": "ditto",
+    "path": "skills/ditto",
+    "category": "agent-behavior",
+    "name": "ditto",
+    "description": "Use when a user asks to mine or update a private, evidence-backed work profile from local Claude Code, Codex, Copilot CLI, or OpenCode sessions.",
+    "risk": "critical",
+    "source": "community",
+    "date_added": "2026-07-14",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "community",
+    "source_repo": "ohad6k/ditto",
+    "license": "MIT",
+    "license_source": "https://github.com/ohad6k/ditto/blob/v0.3.6/LICENSE",
+    "tags": [
+      "personalization",
+      "context-engineering",
+      "session-mining",
+      "agent-memory"
+    ]
+  },
   {
     "id": "django-access-review",
     "path": "skills/django-access-review",
@@ -31098,6 +31165,38 @@
       "security"
     ]
   },
+  {
+    "id": "optim-agent",
+    "path": "skills/optim-agent",
+    "category": "data",
+    "name": "optim-agent",
+    "description": "Guide agent-driven parameter optimization for configurable systems with measurable objectives. Use for HPO, inference tuning, simulations, or RL/control experiments.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-07-15",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "community",
+    "source_repo": "Optim-Agent/optim-agent",
+    "license": "MIT",
+    "license_source": "https://github.com/Optim-Agent/optim-agent/blob/main/LICENSE",
+    "tags": [
+      "optimization",
+      "hyperparameter-optimization",
+      "experiments",
+      "tuning"
+    ]
+  },
   {
     "id": "options-flow-analyzer",
     "path": "skills/options-flow-analyzer",
@@ -40052,6 +40151,41 @@
       "reasons": []
     }
   },
+  {
+    "id": "sshepherd",
+    "path": "skills/sshepherd",
+    "category": "devops",
+    "name": "sshepherd",
+    "description": "Zero-knowledge SSH ops CLI — server health checks, docker/systemd control, log tailing, Postgres introspection, and declarative deploys, without ever exposing credentials to the agent.",
+    "risk": "critical",
+    "source": "community",
+    "date_added": "2026-07-15",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "community",
+    "source_repo": "Antheurus/sshepherd",
+    "license": "MIT",
+    "license_source": "https://github.com/Antheurus/sshepherd/blob/main/LICENSE",
+    "tags": [
+      "ssh",
+      "devops",
+      "cli",
+      "server-ops",
+      "postgres",
+      "deploy",
+      "zero-knowledge"
+    ]
+  },
   {
     "id": "stability-ai",
     "path": "skills/stability-ai",