515 skills · sorted by relevance
Analyze git history to map contributors to security-sensitive files and identify ownership gaps. Estimate bus factor, a measure of dependence on few people, group files that change together, and export CSV or JSON for further analysis.
Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.
Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
The English summary is being prepared. Showing the original description.
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
The English summary is being prepared. Showing the original description.
Write, review, and debug Rust applications, including ownership and borrowing rules that govern memory use. Covers trait-based APIs, explicit error handling, asynchronous work with tokio, and tests with Cargo validation.
Write, review, and refactor Rust code using established conventions for ownership, error handling, type design, and concurrency. It guides safer implementations, avoids unnecessary copying, and organizes modules with a limited public interface.
Coordinate employee offboarding across Okta, Google Workspace, Google Drive, and GitHub. Revoke access, reclaim licenses, and report checklist results, with human approval required for ownership transfers and no account deletion.
Task claiming and ownership tracking for parallel agent execution. Agents claim tasks from a shared queue with file ownership enforcement. Use during parallel execution phases when multiple agents work simultaneously.
The English summary is being prepared. Showing the original description.
Build, migrate, review, and test OpenClaw interfaces with Solid 2. The skill covers state ownership, coexistence with Lit during migration, overlays such as dialogs, performance, and checks that preserve existing interface behavior.
Write and review Rust, C++, and C code with safer memory and resource management. Covers ownership, automatic cleanup tied to scope, and smart pointers to help prevent leaks, double frees, and access to freed memory.
Organize feature development across multiple agents by dividing work, assigning one owner per file, and agreeing on interfaces before implementation. Provides strategies for shared files, branches, and integration so agents can build separate parts of the same system.
Plan Table v9 state ownership across the table, framework state, and external atoms that hold values. Covers initial values, update callbacks, and reset behavior, helping coordinate individual state sections without conflicting owners.
Compares frameworks, libraries, and cloud providers using weighted criteria. Helps teams choose technologies with estimates of five-year total ownership costs, security assessments, community health indicators, and migration effort, risks, and timelines.
Turn a meeting transcript into structured notes and one Linear ticket per action item. Assign owners from the discussion or the team’s ownership map, and flag unclear assignments in unassigned tickets for follow-up.
Write and review Rust code with clear ownership, reference lifetimes, asynchronous tasks, and explicit error handling. Use types to prevent invalid states, reduce unnecessary copying, and document the safety requirements of necessary unsafe operations.
Examine how a job or business generates income through ownership, responsibility, and leverage—ways to expand output beyond personal working hours. Use the framework to consider equity, products, or content while setting limits on downside risk.
Refactor large SwiftUI screens into smaller views with clear inputs and state ownership. Organize actions, shared dependencies, and observable models while preserving existing layout and behavior, making the code easier to read and test.
Assign ready tasks from a project plan to Worker agents and check their submitted results. The skill defines task specifications, file ownership, and result statuses, helping a coordinator decide whether to accept work or plan follow-up tasks.
Review security discovery results to distinguish a target organization’s assets from unrelated assets sharing its name. Check ownership evidence, identify misleading web responses, quarantine uncertain entries, and recalculate severity counts before proceeding with security testing.
Design features such as CRM around reusable database storage and a shared editor. It guides ownership, permissions, API contracts, and update behavior so different applications can use the same database components while enforcing their own access rules.
[omh] Rust ownership, lifetime, or unsafe trouble: prepare Rust changes with ownership, error, and API discipline, and escalate any unsafe, FFI, or lock-free change to the UB checklist. Use when the user says: rust, rust code, rust skill, rustlang, borrow checker, lifetime error, ownership error, trait bound.
The English summary is being prepared. Showing the original description.
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
The English summary is being prepared. Showing the original description.
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
The English summary is being prepared. Showing the original description.