ReddRadar
Topic: openclaw
3,425 skills in this topic.
-
git-workflow
Use this skill when working with git — making commits, creating branches, resolving merge conflicts, opening pull requests, or reviewing diffs. Apply whenever the user asks about version control operations.
aiming-lab/MetaClaw 3,371
-
do-not-retry-without-diagnosis
Common mistake — retrying the same failing command or API call without understanding why it failed. Always diagnose the root cause before retrying anything.
aiming-lab/MetaClaw 3,371
-
debug-systematically
Use this skill when diagnosing a bug, unexpected behavior, test failure, or any situation where code does not behave as expected. Follow a structured debugging process instead of randomly changing code.
aiming-lab/MetaClaw 3,371
-
data-validation-first
Use this skill before any data analysis, transformation, or modeling. Always inspect and validate the data before drawing conclusions or writing transformations.
aiming-lab/MetaClaw 3,371
-
context-window-management
Use this skill in long conversations or multi-turn agentic sessions where context may be lost or the conversation is approaching token limits. Summarize, prioritize, and compact context proactively before it becomes a problem.
aiming-lab/MetaClaw 3,371
-
codebase-navigation
Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes.
aiming-lab/MetaClaw 3,371
-
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
aiming-lab/MetaClaw 3,371
-
avoid-scope-creep
Common mistake — doing unrequested work (refactoring, adding extra features, cleaning up style) when the user asked for a specific, targeted change. Only change what was explicitly asked.
aiming-lab/MetaClaw 3,371
-
avoid-hallucinating-specifics
Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.
aiming-lab/MetaClaw 3,371
-
avoid-acting-on-assumptions
Common mistake — proceeding with assumptions about ambiguous requirements instead of asking a clarifying question first. This skill reminds you to stop and ask before acting on uncertain interpretations.
aiming-lab/MetaClaw 3,371
-
auth-and-authorization-patterns
Use this skill when implementing authentication (login, token issuance) or authorization (access control, permissions). Apply whenever the task involves login flows, JWT, OAuth2, session management, or RBAC.
aiming-lab/MetaClaw 3,371
-
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
aiming-lab/MetaClaw 3,371
-
async-communication-etiquette
Use this skill when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately.
aiming-lab/MetaClaw 3,371
-
agent-task-handoff
Use this skill when delegating a subtask to a sub-agent, spawning a parallel worker, or handing off work across sessions. Write a self-contained task description so the receiving agent needs no prior context.
aiming-lab/MetaClaw 3,371
-
secrets-management
Use this skill when handling API keys, passwords, tokens, private keys, or any sensitive credential. Never hardcode secrets in source code — apply this whenever the word "key", "token", "password", or "secret" appears in the task.
aiming-lab/MetaClaw 3,371
-
robust-error-handling-in-scripts
Use this skill when writing shell scripts, Python automation, or any unattended batch job. Ensure failures are detected, logged, and handled — never silently ignored.
aiming-lab/MetaClaw 3,371
-
structured-research-workflow
Use this skill when conducting research on a topic from scratch — literature review, competitive analysis, technical due diligence, or fact-finding. Apply before starting any open-ended research task.
aiming-lab/MetaClaw 3,371
-
structured-progress-update
Use this skill when summarizing progress on an ongoing project or multi-step task. Give a clear, scannable status report whenever asked for an update or at the end of a work session.
aiming-lab/MetaClaw 3,371
-
structured-logging-and-observability
Use this skill when building production services, pipelines, or automation that needs to be debugged, monitored, or audited. Add structured logs, metrics, and health checks before shipping any service.
aiming-lab/MetaClaw 3,371
-
sql-best-practices
Use this skill when writing SQL queries — selects, joins, aggregations, window functions, or schema modifications. Apply whenever SQL is needed to ensure correctness, safety, and performance.
aiming-lab/MetaClaw 3,371
-
source-evaluation
Use this skill when presenting information from external sources, citing research, or answering factual questions. Assess source credibility and recency before relying on it.
aiming-lab/MetaClaw 3,371
-
secure-code-review
Use this skill when reviewing or writing code that handles user input, authentication, file I/O, network requests, or database queries. Always check for common security vulnerabilities before considering the code complete.
aiming-lab/MetaClaw 3,371
-
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.
aiming-lab/MetaClaw 3,371
-
task-decomposition
Use this skill when a user presents a large, vague goal. Break it into concrete, ordered sub-tasks before starting any work. Apply whenever the request is larger than a single focused action.
aiming-lab/MetaClaw 3,371