What it does
This repo is a collection of 36 skills
- Connects Instruction files the AI reads, with steps that call an outside service
- Account or key Some steps need a key for API_KEY, Anthropic (per the README)
- Category Automatisierung und Agenten
Maker’s original description
🦞 Just talk to your agent — it learns and EVOLVES 🧬.Für Anbieter: Badge ins README
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/aiming-lab-metaclaw)Ähnliche Skills
Gleiche Art Arbeit, sortiert wie die Skill-Liste
36 Skills (Anweisungssammlungen) von aiming-lab, die eine KI liest und befolgt · kein MCP-Server
Pick the skill to install
Install only the ones you use. Open a skill to see how to install it
This set has 36 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below
Showing 30 of 36 See all on GitHub
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
- idempotent-script-design
Use this skill when writing scripts, cron jobs, data pipelines, or any automated process that may be run multiple times. Design every operation to be safely re-runnable without side effects.
- input-validation-and-sanitization
Use this skill when implementing any endpoint, form handler, CLI tool, or function that accepts external input. Validate and sanitize all untrusted data before processing — never assume input is safe.
- plan-before-multi-step-execution
Use this skill before executing a sequence of 3 or more steps, especially when steps are irreversible or depend on each other. Write out the plan and verify it before starting execution.
- prioritize-by-impact
Use this skill when the user has a list of tasks and needs help deciding what to do first. Rank by impact and urgency — not order of mention — and surface the highest-leverage work.
- professional-email-drafting
Use this skill when drafting emails, Slack messages, announcements, or any external/internal communication. Apply professional structure and appropriate tone before writing any message.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Was einen Skill von MCP unterscheidet
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Funktioniert mit
Claude CodeCodexGemini CLI
Laut README des Anbieters und den Ordnern im Repo
Installieren
Pick a skill first
This repo has 36 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Diskussion
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.
Von GitHub
- GitHub-Sterne
- 3.468
Stars are for the whole repo, not each skill - Anbieter
- aiming-lab
- Lizenz
- MIT
- Letzte Codeänderung
- 7. Juni 2026
- SKILL.md-Dateien im Repo (mit Übersetzungen und Vorlagen)
- 30
- Themen
- agent, ai-agent, continual-learning, fine-tuning, llm, lora, meta-learning, metaclaw, online-learning, openclaw, reinforcement-learning, skill-learning