Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

pina-org

@pina-org source repo

10 published skills

  1. ▌
    Create Skill · pina-org
    Create, modify, and improve PINA skills. Use when the user wants to create a new skill for PINA development guidance, edit an existing PINA skill, or add cross-tool compatibility (opencode, Claude Code, Codex CLI) to a skill. Covers skill directory structure, SKILL.md front matter conventions, symlinks for Claude Code compatibility, and updating AGENTS.md for Codex CLI.
    0
    installs
  2. ▌
    Select Model · pina-org
    Guides users through selecting, configuring, or creating a PyTorch model for a PINA problem. Use when the user asks about models, architecture, neural network choice, or how to build/choose a model for their PINA problem. Also triggers on phrases like "what model should I use", "choose a model", "create a model", "neural network", "architecture", "model selection", or when the user mentions specific model names (FeedForward, DeepONet, FNO, PirateNet, etc.).
    0
    installs
  3. ▌
    Pina Workflow · pina-org
    Orchestrates a complete session from problem definition through trained solver. This is the entry point for solving differential equations or physics problems with neural networks. Use when the user has a vague open-ended request like "I have a differential equation", "I want to solve a PDE", "I have a physics problem", "I need to model a system", "help me solve an ODE", "I want to use neural networks for my equations", "I have some data and equations", or "let's build physics-informed neural networks". Also triggers on mentions of specific equations (Navier-Stokes, Burgers, Poisson, heat equation, wave equation, etc.) or when the user describes a physical system they want to simulate. This skill will guide the user through the full workflow step by step, loading the right sub-skills at the right time.
    0
    installs
  4. ▌
    Select Solver · pina-org
    Guides users through selecting the right PINA solver for their problem, or creating a custom solver when no built-in fits. Use when the user asks "what solver should I use", "how do I train this", "which solver", "choose a solver", "pick a solver", "solver selection", "how do I set up training", "what's the right solver", or similar. Also triggers when the user mentions specific solver names (PINN, CausalPINN, SelfAdaptivePINN, SupervisedSolver, etc.) or asks about custom training loops / custom solvers.
    0
    installs
  5. ▌
    Create Problem · pina-org
    Entry point for creating PINA problems. Routes to sub-skills based on problem type (data-driven vs physics-driven), problem class selection, domain setup, equations, conditions, and discretisation.
    0
    installs
  6. ▌
    Define Domains · pina-org
    Create and manipulate domains for PINA physics-driven problems. Covers domain types (Cartesian, Ellipsoid, Simplex), set operations, partial/update methods, and domain discretisation.
    0
    installs
  7. ▌
    Select Trainer · pina-org
    Guides users through configuring the PINA Trainer for solver training, including batching strategy, data splitting, and Lightning options. Use when the user asks "how do I train", "how to train", "set up training", "trainer", "Trainer", "train my model", "fit", "training loop", or similar. Also triggers when the user mentions batching, training configuration, train/val/test split, or is confused about how to start training.
    0
    installs
  8. ▌
    Condition Setup · pina-org
    Set up conditions for PINA problems. Covers data types (LabelTensor, Graph, PyG Data), time series conditions, binding equations to domains, and data-driven input→target mapping.
    0
    installs
  9. ▌
    Define Equations · pina-org bundle
    Define PDEs, ODEs, boundary conditions, and custom equations for PINA physics-driven problems. Covers the equation zoo, custom equation functions, and inverse problem equation signatures.
    0
    installs
  10. ▌
    Skill Sync Checker · pina-org
    Audits SKILL.md files in this repo's skills directory for references to functions, classes, or modules (mentioned by name in prose, e.g. `parse_invoice`) that no longer exist in the codebase because they were renamed, moved, or deleted. Proposes a targeted fix to the one skill being checked, never a blanket rewrite. ONLY use this skill when the user's message begins with the exact phrase "I am a pina developer and I need to check skills are updated with code". This is a deliberate, narrow, internal-only trigger — do not activate this skill for generic requests like "check if my docs are outdated," "review my skills," "are these skills still accurate," or any similar phrasing that lacks that exact opening phrase, even if the underlying intent sounds similar.
    0
    installs