Loading...
Loading...
Found 2,738 Skills
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
Guide users step-by-step through manually testing whatever is currently being worked on. Use when asked to "test this", "verify it works", "let's test", "manual testing", "QA this", "check if it works", or after implementing a feature that needs verification before proceeding.
Deploy and manage live trading agents on Hyperliquid. ⚠️ HIGH RISK - REAL CAPITAL AT STAKE ⚠️ Provides deployment_create (launch agent, $0.50), deployment_list (monitor), deployment_start/stop (control), and account tools (credit management). Supports EOA (1 deployment max) and Hyperliquid Vault (200+ USDC required, unlimited deployments). CRITICAL: NEVER deploy without thorough backtesting (6+ months, Sharpe >1.0, drawdown <20%). Start small, monitor daily, define exit criteria before deploying.
Security-related rules for Tauri application development.
Guidelines for writing Agent Skills. TRIGGERS: create a skill, new skill, write a skill, skill template, skill structure, review skill, skill PR, skill compliance, agentskills spec, SKILL.md format, skill frontmatter, skill best practices
arxiv 논문을 체계적으로 분석하여 Obsidian 서베이 노트를 생성한다. arxiv 페이지/ID를 입력받아 (1) Paper Digest 스타일 핵심 요약, (2) Iterative Writing 원칙 기반 세부 정리, (3) 플로우 다이어그램 포함 Obsidian 페이지를 생성한다. TRIGGERS: "논문 서베이", "paper survey", "arxiv 정리", "논문 노트", "서베이 페이지", "survey note"
This skill should be used when users want to validate or critique an argument by extracting premises, surfacing hidden assumptions, checking logical validity, optionally formalizing in Lean, and researching premise support.
Expert for developing Streamlit data apps for Keboola deployment. Activates when building, modifying, or debugging Keboola data apps, Streamlit dashboards, adding filters, creating pages, or fixing data app issues. Validates data structures using Keboola MCP before writing code, tests implementations with Playwright browser automation, and follows SQL-first architecture patterns.
Define, validate, and run lane-style multi-step automation sequences using `asc workflow` and a repo-local `.asc/workflow.json`. Use when migrating from lane-based automation, building enterprise CI flows, or orchestrating multi-command `asc` runs.
Manual QA testing — verify features end-to-end as a user would, using every tool available (browser, macOS, bash, APIs). Focuses on what formal test suites cannot capture: visual correctness, UX flows, usability judgment, integration reality, edge cases, and failure modes. Standalone or composable with /ship. Triggers: qa, qa test, manual test, test the feature, verify it works, exploratory testing, smoke test, end-to-end verification.
Build public-facing web forms for data collection without Desk access. Use when creating customer submission forms, feedback forms, or self-service portals with Frappe Web Forms.
This skill should be used when running ansible-lint, configuring linting rules, testing Ansible playbooks, validating playbook syntax, or setting up integration tests. Covers ansible-lint configuration and testing strategies.