7K skills · sorted by relevance
Answer NemoClaw maintainer questions using policy references covering issue and pull request assessment, labels, project fields, releases, and competing contributions. It explains the relevant rules in plain language through a read-only workflow.
Configure Google Cloud logs across multiple projects, either by storing them centrally or querying them together where they already reside. The skill guides routing, access permissions, and log views, and helps diagnose missing logs and permission failures.
Find projects, skills, agents, and tools in the Kortix catalog, then adapt their files to an existing project. The skill guides source inspection, configuration merging, and preparation of a change request for user review.
Design, review, and implement Gantt charts for project schedules. Assess source data, task dependencies, and resource needs, then define suitable views, editing behavior, rendering tools, accessibility, exports, and tests—or recommend a clearer alternative.
Package a finished local web project for GitHub with a tailored README and a preview from the running project. Audit files before pushing, publish compatible projects through GitHub Pages, and verify the repository and live demo.
Guides LoopX project setup and repair, including goal configuration, shared registry synchronization, stale dashboard status, and command-line routing issues. It distinguishes project lifecycle maintenance from ordinary task execution and directs each operation to its relevant procedure.
Inspect a project and create or update CLAUDE.md files that give an AI agent project context. Summarize architecture and shared rules at the root, document individual modules, and report diagrams, navigation links, and scanning gaps.
Diagnose why MSBuild builds across multiple projects fail to run efficiently in parallel. Use build logs and project dependencies to identify blocking chains, then recommend changes to references, scheduling, or parallel execution settings.
Organize shared build settings, tasks, and package versions across .NET projects. Review Directory.Build file placement and import order, centralize repeated configuration, and retain the settings that belong to individual projects or folders.
Use this skill for any work involving a MATLAB Project (.prj file) — creating a new project, tracking files, managing the project path, configuring Simulink cache and code-generation folders, running project health checks, or writing build scripts that keep the project in sync with the file system. Trigger phrases include "set up a MATLAB project", "create a .prj", "track this file in the project", "project health check", "build script conventions". This skill is the generic foundation; domain-specific skills (e.g. `mbse-workflow`) build on it.
The English summary is being prepared. Showing the original description.
Initialize the UniKit framework in a project. Scans the current project to detect the engine and real tech stack, then generates the base framework documents that give AI agents context about the project — the resolved project description, the architecture doc, AGENTS.md, and the user-editable .unikit/config.yaml. This is the one-time, whole-project setup run before any other unikit skill. Use whenever the user wants to initialize, set up, or onboard the framework, e.g. "initialize unikit", "init the framework", "set up unikit", "set up the project", "configure AI context", "scan my project and set it up", "bootstrap the project". It also actualizes the config of a project already set up — say "update the config", "add missing settings", "actualize configuration", "fix my config".
The English summary is being prepared. Showing the original description.
Choose research problems, refine new ideas, or rethink stalled projects through structured conversation. Assess feasibility, potential impact, and risks, then develop success criteria, decision points, and backup plans for a clearer research strategy.
Import an external plan into GSD after checking it against recorded project decisions, then validate the resulting plan file. It also supports converting a GSD-2 project back to the GSD v1 planning format.
Set up a new project by gathering context, optionally researching the domain, defining requirements, and building a roadmap. It creates planning files that record the project’s background, workflow preferences, phased structure, and ongoing state.
Organize research knowledge by project in Obsidian, from creating folder structures and routing notes to maintaining daily logs, plans, and indexes. It also manages note changes and coordinates checks for broken links and registry consistency.
Migrate legacy .NET project files to SDK-style format, reducing repetitive XML and explicit file lists. Convert package references, move assembly metadata into project settings, and consolidate shared build and package settings across multiple projects.
Manage the lifecycle of an Obsidian project knowledge base by stopping sync, archiving content, or permanently deleting it on explicit request. It also handles individual note archiving, deletion, and renaming with link repair, then summarizes the resulting state.
Set up an Obsidian knowledge base for a research repository containing code and Markdown. It creates project links, planning notes, source inventories, and code summaries, importing structure and summaries while leaving large research artifacts out.
Set up a research project with separate folders for code, source data, cleaned datasets, results, and documents. Create a research rules file from a template, a project README, and an initial progress log.
Get guidance on setting up OpenKnowledge for shared Markdown editing, sharing a project with collaborators, and previewing individual files. Explains setup commands and viewing options for agent environments, Claude Desktop, and the macOS desktop app.
Review a project’s past Codex sessions, saved memory, and existing skills to identify recurring workflows. Receive prioritized recommendations for updating incomplete skills or creating distinct new ones, grounded in actual project history.
All-in-one project configuration and health management. Sets up new projects (settings.local.json, CLAUDE.md, .gitignore), audits existing projects (permissions, context quality, MCP coverage, leaked secrets, stale docs), tidies accumulated cruft, captures session learnings, and adds permission presets. Uses sub-agents for heavy analysis to keep main context clean. Trigger with 'project health', 'check project', 'setup project', 'kickoff', 'bootstrap', 'tidy permissions', 'clean settings', 'capture learnings', 'audit context', 'add python permissions', or 'init project'.
The English summary is being prepared. Showing the original description.
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding templates (use template-discovery), producing a detailed side-by-side comparison of templates (use template-comparison), authoring custom templates (use template-authoring), deciding cross-parameter defaults such as which framework to pair with native AOT or whether to keep HTTPS when auth is enabled (use template-smart-defaults), modifying existing projects or adding NuGet packages to existing projects.
The English summary is being prepared. Showing the original description.
Full project initialization wizard from ProjectConfig, including folders, packages, Git, and MCP setup. Use when setting up a new Unity project from scratch, creating the folder structure, or bootstrapping infrastructure. Triggers on requests like "set up a new project", "create folder structure", "initialize the project", or "/uw-cmd-setup-project". Reads ProjectConfig.yaml for all decisions.
The English summary is being prepared. Showing the original description.