Write Yo async code and algebraic effect handlers. Use this when working with IO, Future, JoinHandle, using/given, io.async, io.await, io.spawn, return, and escape.
Neues Projekt im aktuellen Workspace verknüpfen — nur Projekt-ID in project.json schreiben
Build resilient, type-safe HTTP integrations with trembita using Result-based error handling, retries, and circuit breaker patterns. --- # Trembita Skill Use this repository as a practical reference for agents implementing HTTP clients with `trembita`. ## When to Use - Build TypeScript integrations for third-party REST APIs. - Add robust error handling without exception-driven control flow. - Implement retries, circuit breakers, and timeouts with minimal dependencies. - Write testable API code by injecting `fetchImpl`. ## Core Patterns 1. Initialize once with `createTrembita()` and handle init `Result`. 2. Use `client.request()` for parsed JSON body responses. 3. Use `client.client()` when you need HTTP metadata (`statusCode`, `body`). 4. Narrow failures by checking `result.error.kind`. 5. Add resilience via `createRetryingFetch` and `circuitBreaker` config. ## Canonical References - `README.md` - quick overview and install. - `QUICK_START.md` - shortest path to first success. - `LEARNING_GUIDE.md` - concepts and progressive examples. - `EXAMPLES.md` - production-style patterns. - `ARCHITECTURE.md` - request/error flow diagrams. ## Agent Guardrails - Prefer `Result` handling over `try/catch` for request outcomes. - Keep endpoint configuration explicit and validated. - Prefer `expectedCodes` to document acceptable HTTP outcomes. - Use `client.client()` for 404/202 branching by status code. - Inject `fetchImpl` in tests; avoid global fetch patching.
Architecture patterns, code generation guides, and reference documentation for building Prismatic custom components.
Guides users through a stricter 7-step agile PM workflow. Invoke when users have a rough product idea and need interactive HTML prototype, PRD, mermaid flowcharts, and versioned delivery.
Teaches agents how to operate within Open Station — find tasks, execute work, update state, and store artifacts.
Manage authentication for Get笔记 CLI
Living Architecture Map — auto-generate Mermaid diagrams of your codebase. Use when user wants to visualize architecture, understand code structure, generate diagrams, or document system design.
Runs multi-pass automated code review with per-issue fix subagents. Triggers when preparing a branch for PR, reviewing code changes, or when thorough automated code quality review is needed.
Create or modify a platform adapter with web research, implementation, testing, and D09 checklist verification.
Gate DEX read-only market data skill. Use when the user asks for prices, K-lines, rankings, holders, or liquidity without signing a tx. Triggers on 'DEX price', 'token K-line', 'holder analysis'. Do NOT use for swaps or wallet auth — use gate-dex-trade or gate-dex-wallet.
Cadence's execution phase. Advances implementation, validation, and status writeback based on existing and continuable issue files; entering this phase when directly requested by the user is also considered entering Cadence. If there is no clear issue file or the target is unclear, ask the user to specify.
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
