2.6K skills · sorted by relevance
Set up a managed Kubernetes environment on Google Cloud, from choosing Autopilot or Standard to creating a GKE cluster, obtaining kubectl connection credentials, and deploying workloads. Includes guidance on private clusters and resource requests.
Update existing Lattice standards after a significant change — the update-mode counterpart to lattice-init. Scans .lattice/standards/, asks what changed, and routes each affected standard to its refiner's revise mode, recording a git-native change note. Use when the user says 'update refiners', 'refiners update', 'our standards changed', 'update our standards', 'the architecture changed, update the standards', 'we switched languages, update the standards', 'revise standards after a big change', or 're-run the refiners'.
The English summary is being prepared. Showing the original description.
Audit and strengthen security for applications running on GKE. Configure pod traffic restrictions, sandbox isolation, namespace security standards, and Secret Manager volume mounts to protect workloads at the application and namespace level.
Apply Apache ShardingSphere’s written coding standards during implementation or review, covering naming, Java constructs, tests, and Maven dependencies. Also audit a specified scope without editing files, combining automated checks with manual inspection of applicable rules.
Set up Ruflo in a new repository using an interactive wizard or the standard preset. Create project instructions and configuration files, including MCP server registration so the agent can access the ruflo tools.
Plan and create Google Kubernetes Engine clusters using templates for production, development, or AI workloads. Compare Google-managed and self-managed node options, review configurations before creation, and check settings for production readiness.
Plans, executes, and validates Google Kubernetes Engine upgrades for Standard and Autopilot clusters. Creates environment-specific upgrade plans, checklists, and command-based runbooks, with guidance on maintenance timing, node upgrade strategies, workload readiness, and stalled upgrades.
Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.
The English summary is being prepared. Showing the original description.
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution, customising its embedded defaults for the team's product process. Use when setting up a new project, defining product standards, or when the user says 'set up requirement standards', 'define feature standards', 'configure requirement forge', 'define how features should be structured', or 'requirement forge refiner'.
The English summary is being prepared. Showing the original description.
Signpost (not a knowledge pack) for the ECSS European space standards: the E-ST-10 system engineering family, the discipline standards a reader commonly mis-cites (radiation is E-ST-10-12, not a RAM standard; software is E-ST-40, not E-ST-70), the M-branch project management standards, the Q-branch product assurance standards, and the sustainability and system documents, with designation, edition, owner, status, and catalogue URL only. Contains no source content. Free process paths are existing NASA packs in this catalogue, named by slug, and are not ECSS clause substitutes. Several needs have no in-repo pack.
The English summary is being prepared. Showing the original description.
Signpost (not a knowledge pack) for the systems-engineering standards landscape — ISO/IEC/IEEE 15288, 24748, 29148, 42010, 15026, 24765; INCOSE SE Handbook & Vision 2035; OMG SysML; SAE/EIA 1001/649/748; ECSS space standards; NATO AAP-48; CMMI; NIST SP 800-160; and more. Contains NO source content: it lists each standard's designation, title, purpose, owning SDO, whether it's redistributable, and where to get it. Use when you need to identify or locate an SE standard — most are paywalled/all-rights-reserved and cannot be packaged, so this points you to the owner (and to the open packs where one exists).
The English summary is being prepared. Showing the original description.
Knowledge base from the OUSD(R&E) guidebook Implementing a MOSA in DoD Programs (Feb 2025). Use for the Modular Open Systems Approach as a DoD acquisition + design discipline: the statutory/regulatory basis (10 U.S.C. 4401–4403, FY2017/FY2021 NDAA, DFARS), the five OUSD(R&E) pillars, the plan→modularize→identify→define→standardize interface lifecycle, technical levers (WBS/MIL-STD-881F taxonomy, standards profiling, API-first software, COTS/cybersecurity), MOSA assessment metrics and tools (PART/OAAT/KOSS/SEAM/MAUT), technology-change and DMSMS management, roadmaps, MOSA across the six AAF pathways, and contracting/IP/data-rights mechanics. SCOPE LIMITS: this is U.S. DoD weapon-system acquisition policy, not a general open-architecture or interface-standards reference — it names standards (FACE, OMS, DISR) without reproducing them, is light on detailed engineering of any specific standard, and does not cover the underlying SE processes (use dau-se-guidebook / nasa-npr-7123) or general systems-engineering theory (use sebok).
The English summary is being prepared. Showing the original description.
Standardizes molecular structures using ChEMBL chembl_structure_pipeline and RDKit rdMolStandardize covering sanitization, salt/solvent stripping, neutralization, tautomer canonicalization, stereochemistry standardization, mixture handling, and isotope normalization. Explicitly compares ChEMBL pipeline, canSARchem, and PubChem standardization choices. Use when preparing libraries for QSAR training, joining datasets across sources, deduplicating compound collections, or building canonical compound registries.
The English summary is being prepared. Showing the original description.
Standardizes molecular structures using ChEMBL chembl_structure_pipeline and RDKit rdMolStandardize covering sanitization, salt/solvent stripping, neutralization, tautomer canonicalization, stereochemistry standardization, mixture handling, and isotope normalization. Explicitly compares ChEMBL pipeline, canSARchem, and PubChem standardization choices. Use when preparing libraries for QSAR training, joining datasets across sources, deduplicating compound collections, or building canonical compound registries.
The English summary is being prepared. Showing the original description.
Standardizes molecular structures using ChEMBL chembl_structure_pipeline and RDKit rdMolStandardize covering sanitization, salt/solvent stripping, neutralization, tautomer canonicalization, stereochemistry standardization, mixture handling, and isotope normalization. Explicitly compares ChEMBL pipeline, canSARchem, and PubChem standardization choices. Use when preparing libraries for QSAR training, joining datasets across sources, deduplicating compound collections, or building canonical compound registries.
The English summary is being prepared. Showing the original description.
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
Define project quality standards in CONSTRAINTS.md, connect measurable targets to checks, and inspect changes for weakened safeguards. It helps teams choose thresholds and catch skipped tests, suppressed warnings, unfinished code, or lowered standards during agent development.
Process molecular datasets in Python through a simpler interface to RDKit, a chemistry toolkit. Convert and standardize structures, calculate molecular properties, compare and cluster compounds, generate 3D conformations, and visualize results for drug discovery workflows.
Convert laboratory instrument files into Allotrope Simple Model (ASM) JSON, a standardized data format, or tabular CSV. Detect instrument types, validate converted data, and export Python parsing code for analysis workflows or handoff to data engineers.
Find CAD models of off-the-shelf parts on step.parts using model names, standards, aliases, and dimensions. Compare matching records, download STEP files when needed, and check file integrity against a supplied checksum.
Create or update Kubernetes YAML configuration files for GKE Autopilot and Standard. Translates application requirements into manifests covering container permissions, CPU and memory allocation, health checks, storage, external routing, and GPU resources for AI model serving.
Prepare a first-pass review of incoming NDAs, or confidentiality agreements, against a team's standard positions. The skill saves the document, drafts suggested clause changes, and prepares a counsel summary without signing or sending anything.
Build a custom fuzzer, a tool that tests code with many generated inputs, using LibAFL in Rust. Combine input mutation, execution feedback, scheduling, and target execution components when standard fuzzers offer insufficient control.
Turn a prepared outline into consistently designed HTML slides, PNG previews, speaker notes, and a presentation page. The skill reviews rendered pages for visual issues and exports a PPTX file when the output settings require one.