Explorar skills

Defines the coding standards, patterns, and conventions for ASP.NET Core REST API controllers. Rules cover routing, HTTP verbs, response types, XML documentation, dependency injection, and asynchronous execution. Apply these rules uniformly to ensure a consistent, predictable, and well-documented API surface.

Discovers available agents, skills, quality commands (lint, test, typecheck), and tech stack in the project environment. Use when starting implementation, creating PRs, reviewing PRs, or addressing feedback to determine which agents to dispatch and which quality commands to run. Use before workflow execution to adapt gh-workflow commands to project-specific tooling.

Esta skill remove padrões de escrita de IA, reduz a taxa de plágio e humaniza textos gerados por IA, otimizando a taxa de detecção de plágio de 60% para menos de 30%.

Use automatically after creating any new Obsidian note to surface hidden connections with existing notes. Also use whenever the user asks 'find related notes', 'are there similar notes', 'connect this to others', or reviews a note for cross-references. Shows ranked suggestions with 'why relevant' explanations — does NOT auto-apply.

Search past session observations using the sessions.search MCP tool. Falls back to CLI if the MCP server is not available.

Compare original site vs implementation with automated AE/SSIM diff — near-zero vision tokens. Triggers on "it looks different", "doesn't match", "compare with original", "what's wrong", "why is the impl off", "diff against ref", "verify the clone". Uses auto-diagnose to find mismatched elements from diff images without vision tokens. Falls back to reading diff images only when auto-diagnose finds

Manage the aomi skill distribution pipeline. Trigger when the user asks about platform submission status, wants to push a skill update to a distribution channel, needs to add a new platform, wants to check staleness, or asks about any platform in _registry.yaml, including PR #679, PR #575, PR #21, issue #36, clawhub, codex-marketplace, agensi, lobehub, or anthropic submission.

Step-by-step guide for creating enriched CryptoSkills agent skills. Use when building new protocol skills, contributing to the directory, or understanding the enriched skill pattern. Covers SKILL.md structure, YAML frontmatter, examples, docs, resources, templates, marketplace registration, and validation. Triggers: "create a skill", "add a protocol", "contribute a skill", "new skill template".

{{ ƔƔƔ }} Create a draft pull request to main

Deserialization vulnerability audit skill with gadget chain knowledge for all major languages. Trigger when the user asks to: "audit deserialization", "check for insecure deserialization", "find pickle vulnerabilities", "Marshal.load audit", "gadget chain analysis", "check for unsafe YAML loading", or when reviewing code that processes serialized data (JSON with type info, YAML, XML, binary format

Evidence-bound transformation of vague human requirements (Jira ticket, Confluence page, free text, file path) into AI-ready specifications for coding agents. Use WHENEVER user asks to /distill, "analyze requirements", "clarify task", "vague requirements", "ambiguous AC", "task vs bug", "EARS", "Given-When-Then", "GWT", "AI-ready spec", "prepare spec for implementation", "Open Questions", "INVEST"

Use when working with SAP Controlling (CO) — Cost Element Accounting, Cost Center Accounting, Internal Orders, Profit Center Accounting, CO-PA, Product Costing, Material Ledger, or period-end allocation cycles in any S/4HANA or ECC implementation.