104 skills · sorted by relevance
Investigate queued or slow OpenClaw CI jobs, the automated checks run during development. Use measured evidence to adjust runner capacity, registration budgets, parallel job limits, test grouping, and placement between GitHub-hosted runners and Blacksmith.
Run installation, integration, and end-to-end tests that follow real user actions in remote environments or Docker. Choose an appropriate isolated environment, inspect failures, record execution details, and clean up resources after testing.
Run OpenClaw tests and reproduce bugs on remote machines through Crabbox. Choose a suitable execution provider, verify realistic user workflows, and report the actual provider, environment ID, logs, and timing.
Genre anatomy from John Truby's The Anatomy of Genres (类型解剖 / 类型节拍 / 混合类型 / 超越类型) — genres as beat systems with a life philosophy underneath; three rules (hit every beat of your genre, mix three or four genres, transcend the primary genre), the ladder and families of twelve genres (Horror 恐怖, Action 动作, Myth 神话, Memoir and Coming-of-Age 回忆录与成长, Science Fiction 科幻, Crime 犯罪, Comedy 喜剧, Western 西部, Gangster 黑帮, Fantasy 奇幻, Detective and Thriller 侦探与惊悚, Love 爱情), each with its hero/opponent/world/plot-shape template, beat list, hard rules with failure conditions, subgenres and transcendent paths, plus a genre-mixing worksheet and a diagnostic. Kept beside sw-truby-anatomy and the Field/Snyder page maps. Use when choosing or confirming a script's genre, when a genre story feels generic or misses the beats its audience expects, when mixing genres, when a horror lacks pressure, an action lacks plot, a love story lacks opposition or a detective story lacks reveals.
The English summary is being prepared. Showing the original description.
Use Crabbox for ClawBench remote Linux validation. Default to Blacksmith Testbox; includes direct Blacksmith and owned AWS fallback notes when Crabbox fails.
The English summary is being prepared. Showing the original description.
Research 3–5 confirmed same-industry or cross-industry websites and translate their brand narrative, page architecture, art direction, and visual-system evidence into one reusable Visual Reference Brief. Use when strong references are scarce, a site needs brand-led or premium positioning, a page lacks a narrative spine, or a key module lacks a credible design precedent. Do not create page content, a Design System, UI directions, HTML, or a permanent brand gallery.
The English summary is being prepared. Showing the original description.
リポジトリの構造・技術スタック・機能一覧・セットアップ手順を動的に解析し、 包括的なドキュメントを自動生成するスキル。言語・フレームワーク問わず汎用的に動作する。 Use this skill whenever the user asks to: - Explain a repository / リポジトリの説明 / リポジトリの概要 - Generate a README / README生成 / README作成 - Understand project structure / プロジェクト構成を教えて / 構造を説明して - Learn how to run a project / 使い方を教えて / 動かし方 / セットアップ方法 - Get a repo overview / repo overview / explain this repo / what does this repo do - List features / 機能一覧 / このプロジェクトは何ができる？ - Onboard to a new codebase / コードベースのキャッチアップ / 新しいリポジトリに入った - "このリポジトリ何？" "プロジェクトの全体像" "how to run this project" - "コードの全体を把握したい" "ドキュメントを整備して" "技術スタックを知りたい" This skill is especially useful when joining a new project, onboarding team members, or when a repository lacks proper documentation. It works with ANY repository regardless of programming language, framework, or project type.
The English summary is being prepared. Showing the original description.
Build Java applications with tinystruct, including actions usable from both a terminal and the web. Get guidance on launcher generation, routing, JSON responses, database storage, tests, and MCP tools that agents can call.
Gather relevant code and background for subagents, agents assigned part of a larger task. Search broadly, assess each file, identify missing information, and refine the search for up to three cycles to assemble context for bug fixes or feature work.
Find code that lacks test coverage and get suggestions for tests to add next. Focus on a chosen path, inspect gaps against a coverage threshold, or use a background worker for recurring checks after feature changes.
Finds a local MCP server, a connector that adds tools to an agent, when existing tools or simple code cannot handle a task. It selects packages requiring no environment variables and starts them after approval.
Create a clear, concise README.md after reviewing the project and workspace. Uses example READMEs to guide structure and tone, formats the result for GitHub, and includes an existing project logo or icon when available.
Assess Bluetooth Low Energy devices by capturing wireless traffic, inspecting available data services, and checking pairing security. Identify signs of interception, reused commands, and data access that lacks authentication.
Revise AI-generated drafts by identifying stock phrases, vague claims, and repetitive rhythms. Use audience details and brand writing examples to produce a more natural voice, with annotated feedback and before-and-after comparisons.
Add business knowledge missing from a Wren project's database definitions. Compare source documents with existing context, then add explanations, rules, SQL examples, and proposed metrics through guided questions or an automatic mode with an audit report.
Guides custom map imports into CARLA on UE 5.8, from FBX geometry and OpenDRIVE road data to packaging or temporary road generation. Helps choose a supported route and verify map files and loading.
Examine career and collaboration choices through the principal-agent problem: differences between an owner's interests and those of someone acting for them. The skill helps assess how rewards connect to value created and where partners' incentives may diverge.
Explore personal meaning by reflecting on significant experiences, sacrifices, and mortality. Develop a one-sentence statement of what matters, then reconsider how to spend limited time using a monthly question about having one year left.
Change a running OpenRig setup by adding or removing agent seats, connecting existing sessions, or attaching terminals. Guides checks for roles, startup context, permissions, and session identity so the setup reflects each change correctly.
Use attached spreadsheets and documents as the primary source for reports and analysis. Identify relevant files, extract needed data, and cite filenames, turning to external searches or clearly labeled estimates only when the supplied material lacks required information.
Verify production fixes by connecting code changes and releases to Sentry issues. Compare error events and affected users before and after release, then report whether the fix worked, improved behavior, failed, or lacks enough traffic to judge.
Refine wood materials and lighting in three.js interiors using procedural grain, window light, contact shadows, rays, and dust. A runnable scorecard measures eight aspects of the rendered image, helping guide revisions toward a chosen target score.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
The English summary is being prepared. Showing the original description.
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
The English summary is being prepared. Showing the original description.