change-grug

Manage Grug and Grugformer experiment modifications with a template-first workflow.

1.2k|146|Updated Mar 22, 2024
One-click install
npx skills add https://github.com/marin-community/marin --skill change-grug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-grug
Source: https://github.com/marin-community/marin/tree/main/.agents/skills/change-grug
Command: npx skills add https://github.com/marin-community/marin --skill change-grug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires grug_dir_diff.py, pre-commit.py, test_grug_variant_contracts.py, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of modifying, adding, or updating Grug/Grugformer model variants by providing a structured, template-first workflow.

Core Features & Use Cases

  • Template-First Workflow: Manages changes originating from experiments/grug/base/ and its variants.
  • Experimentation & Upstreaming: Facilitates trying changes in experiment copies before integrating them into the base template.
  • Documentation & Validation: Ensures experiments are recorded and validated through defined steps.
  • Use Case: When tasked with improving a Grug model's attention mechanism, you would use this skill to experiment with changes in a variant directory, document the results, and then upstream the successful modifications back to the base template.

Quick Start

Use the change-grug skill to experiment with a new MLP configuration in a Grug variant.

Frequently Asked Questions about change-grug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage changes to Grug model variants without breaking the base template?

To manage changes to Grug model variants safely, use a template-first workflow that isolates modifications in variant directories before upstreaming successful experiments back to the base template. This approach maintains reproducibility and prevents unvalidated changes from breaking the base.

What is a template-first workflow for Grug and Grugformer experiments?

A template-first workflow for Grug experiments means originating structural changes from the base template, testing them in isolated variant directories, and documenting results. You upstream only successful modifications to ensure validated, reproducible model improvements.

How do I upstream successful modifications from a Grug experiment variant?

To upstream successful Grug experiment modifications, you validate the changes in the variant directory, document the experiment results, and then integrate the tested modifications back into the base template for future variant generation and reproducibility.

Does the Grug experimentation workflow integrate with pre-commit hooks for validation?

Yes, the Grug experimentation workflow integrates with pre-commit hooks to validate changes. This ensures that modifications in variant directories meet defined contract criteria before being documented and upstreamed to the base template.

When should I use a variant directory for Grug model experimentation?

You should use a variant directory for Grug model experimentation when you need to test changes to components like an MLP configuration or attention mechanism. It allows you to document results and validate modifications before affecting the base template.