Probe gizmo definitions. Use when the user asks to "run the gizmo probe", "probe a gizmo", or "check my gizmo".
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add yaniv-golan/skill-creator-plus --skill gizmo-probe --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gizmo Probe?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yaniv-golan-gizmo-probe)More formats (shields.io, HTML) on the badges page.
---
name: gizmo-probe
description: Probe gizmo definitions. Use when the user asks to "run the gizmo probe", "probe a gizmo", or "check my gizmo".
---
# Gizmo Probe
When the user asks to run the gizmo probe, run this skill's probe script with `--selftest` and
report the exact line it printed. The script needs no input file; do not ask for one.
**Running this skill's scripts.** Prefer the absolute path this file was loaded with:
python3 ${CLAUDE_SKILL_DIR}/scripts/probe.py [args]
If the shell reports that path missing, you are on a host where the shell and the file tools are
different mounts of the same content (Cowork's host loop). **Do not guess, rewrite, or transform
that path** — the mapping is not something you can infer, and a guessed path that happens to work
is luck. Locate the file from the SHELL's side and run exactly what it finds:
find / -path "*gizmo-probe/scripts/probe.py" -print -quit 2>/dev/null
Do not type `$CLAUDE_SKILL_DIR` or `$CLAUDE_PLUGIN_ROOT` into a shell command. Neither is
exported: the first expands to nothing, and the second may be set to a *different* plugin's
directory, so checking whether it is empty will not tell you it is wrong.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
