Monitor and query Claude Code sessions — list sessions, search conversations, check costs, view AI fluency score, see live running agents. Use when the user asks about their Claude Code usage, costs, session history, or running agents. --- ## You operate the `claude-view` HTTP API **If the claude-view MCP tools are available in your environment, prefer using them instead of curl.** This skill is the fallback for environments without MCP support. claude-view runs a local server on port 47892 (or `$CLAUDE_VIEW_PORT`). All endpoints return JSON (camelCase field names). Base URL: `http://localhost:47892` ## Resolving the server 1. Check if running: `curl -sf http://localhost:47892/api/health` 2. If not running, tell user: `npx claude-view` ## Endpoints | Intent | Method | Endpoint | Key Params | |--------|--------|----------|------------| | List sessions | GET | `/api/sessions` | `?limit`, `?q`, `?filter`, `?sort`, `?offset`, `?branches`, `?models`, `?time_after`, `?time_before` | | Get session detail | GET | `/api/sessions/{id}` | — | | Search sessions | GET | `/api/search` | `?q` (required), `?limit`, `?offset`, `?scope` | | Dashboard stats | GET | `/api/stats/dashboard` | `?project`, `?branch`, `?from`, `?to` | | AI Fluency Score | GET | `/api/score` | — | | Token stats | GET | `/api/stats/tokens` | — | | Live sessions | GET | `/api/live/sessions` | — | | Live summary | GET | `/api/live/summary` | — | | Server health | GET | `/api/health` | — | ## Reading responses All responses are JSON with camelCase field names. Key shapes: **Sessions list:** `{ sessions: [{ id, project, displayName, gitBranch, durationSeconds, totalInputTokens, totalOutputTokens, primaryModel, messageCount, turnCount, commitCount, modifiedAt }], total, hasMore }` **Session detail:** All session fields plus `commits: [{ hash, message, timestamp, branch }]` and `derivedMetrics: { tokensPerPrompt, reeditRate, toolDensity, editVelocity }` **Search:** `{ query, totalSessions, totalMatches, elapsedMs,
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
Complete guide for AI agents to understand, install, and operate ZhiYing
Drift doc-to-code anchor conventions. Use when editing code that is bound by drift docs, updating docs, working with drift.lock, or when drift check reports stale anchors.
Comprehensive guide for building Chrome extensions with Manifest V3. Use this skill whenever the user mentions Chrome extension, browser extension, manifest.json, content script, service worker (in extension context), popup, side panel, chrome.runtime, chrome.tabs, chrome.storage, chrome.scripting, background script, MV3, Manifest V3, or any Chrome extension API. Also trigger when the user wants to inject scripts into web pages, communicate between page and background, bypass CSP from a content script, build an RPC layer over chrome messaging, or publish to the Chrome Web Store. Covers both new extension projects and adding features to existing ones. Do NOT use for framework-specific questions.
Use this skill when developing Node.js backend services or CloudBase cloud functions (Express/Koa/NestJS, serverless, backend APIs) that need AI capabilities. Features text generation (generateText), streaming (streamText), AND image generation (generateImage) via @cloudbase/node-sdk ≥3.16.0. Built-in models include Hunyuan (hunyuan-2.0-instruct-20251111 recommended), DeepSeek (deepseek-v3.2 recommended), and hunyuan-image for images. This is the ONLY SDK that supports image generation. NOT for browser/Web apps (use ai-model-web) or WeChat Mini Program (use ai-model-wechat).
Execute commands in isolated sandboxes for security. Use when running untrusted code, system commands, or operations that could affect the host system. Automatically detects the right runtime (Python, Node, Rust, Go, Ruby, etc.) from the command.
Merge the current PR, wait for merge queue/checks to complete, then switch to main and pull
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
Tycono usage guide and project understanding.
Query the BCRA (Banco Central de la República Argentina) Central de Deudores API to check the credit status of individuals or companies in Argentina's financial system. Use when the user asks to check someone's debt situation, credit report, financial standing, rejected checks, or credit history using a CUIT/CUIL/CDI number. Also use when the user mentions "central de deudores", "situación crediticia", "deudas BCRA", "cheques rechazados", "historial crediticio", "informe crediticio", or wants to know if a person or company has debts reported in Argentina's financial system. --- # BCRA Central de Deudores Query Argentina's Central Bank debtor registry to obtain credit reports by CUIT/CUIL/CDI. ## API Overview - **Base URL**: `https://api.bcra.gob.ar` - **Auth**: None required (public API) - **Format**: JSON responses - **Input**: CUIT/CUIL/CDI as integer (no hyphens), e.g. `20123456789` - **Optional web interface**: `https://compara.ar/deudores/:cuit` (replace `:cuit` with the 11-digit CUIT/CUIL/CDI) ## Endpoints ### 1. Current Debts — `GET /centraldedeudores/v1.0/Deudas/{Identificacion}` Returns the latest reported debt situation across all financial entities. ```bash curl -s "https://api.bcra.gob.ar/centraldedeudores/v1.0/Deudas/20123456789" ``` **Response structure:** ```json { "status": 200, "results": { "identificacion": 20123456789, "denominacion": "NOMBRE DE LA PERSONA", "periodos": [ { "periodo": "2024-12", "entidades": [ { "entidad": "BANCO DE LA NACION ARGENTINA", "situacion": 1, "fechaSit1": "2020-03-15", "monto": 150.0, "diasAtrasoPago": 0, "refinanciaciones": false, "recategorizacionOblig": false, "situacionJuridica": false, "irrecDisposicionTecnica": false, "enRevision": false, "procesoJud": false } ] } ] } } ``` ### 2. Historical Debts — `GET /centraldedeudores/v1.0/Deudas/Historicas/{Identificacion}` Returns debt history across multiple periods. Useful for tracking how a debtor's situation evolved over time. ```bash curl -s "https://api.bcra.gob.ar/ce
- 📁 .github/
- 📁 agents/
- 📁 commands/
- 📄 .gitignore
- 📄 CHANGELOG.md
- 📄 LICENSE
Multi-agent orchestration framework for Claude Code. Automatically delegates tasks to cheaper, faster sub-agents (Haiku 4.5, Sonnet 4.6) while maintaining Opus-level quality through verification. Use when working on any coding task — Hydra activates automatically to route file exploration, test running, documentation, code writing, debugging, security scanning, and git operations to the optimal agent. Saves ~50% on API costs. --- # 🐉 Hydra — Multi-Headed Speculative Execution > *"Cut off one head, two more shall take its place."* > Except here — every head is doing your work faster and cheaper. ## ⛔ MANDATORY PROTOCOLS — NEVER SKIP These protocols are NON-NEGOTIABLE. Skipping them is a framework violation. ### Protocol 1: Sentinel Scan After Code Changes When ANY agent returns output containing `⚠️ HYDRA_SENTINEL_REQUIRED`, you MUST — before doing ANYTHING else, before presenting results to the user, before running any other agents — dispatch hydra-sentinel-scan with the files and changes listed in the trigger block. **This is blocking.** The user does NOT see the code changes until sentinel completes. If you present code changes to the user without running sentinel first, you have violated the framework's core safety guarantee.
