skill-system-gate
Configurable gate validation skill. Use when running repository-local gate rules from gate_rules.yaml (command/structural/eda-contract), checking legacy experiment registry safety, or enforcing close-gate fail-closed validation.
What this skill does
# Skill System Gate
Enforce a fail-closed gate before experiment registration and provide read-only registry safety/status checks.
## Decision Matrix
| Task Intent | Operation | Primary Backend | Use When |
|---|---|---|---|
| Validate repository artifacts against configurable gate rules | `validate` | `scripts/gate_validate.py` | Before close-gate decisions or deterministic policy checks |
| Validate experiment implementation and logs against gate rules | `validate-experiment` | `preprocess_lib.gate_engine` | Legacy GNN/FraudDetect pipeline checks |
| Check whether registry state is safe for rerun/reset | `verify-registry` | `db_registry.DBExperimentsDB` | Before any manual reset/rerun action |
| View queue health and state counts | `status` | `db_registry.DBExperimentsDB` | Need a quick dashboard of current experiment states |
## Core Patterns
### Pattern 1: Validate repository gate compliance
```bash
python3 scripts/gate_validate.py --rules config/gate_rules.yaml --artifact-root .
```
- Load configurable `gate_rules.yaml`.
- Support rule types: `command`, `structural`, `eda-contract`.
- Emit markdown verdict and JSON summary on the last line.
### Pattern 2: Validate legacy experiment gate compliance
```bash
scripts/validate_exp.sh <exp_name> [phase_root]
```
- Load `gate_bank.json` rules.
- Run all rule classes (`source_contains`, `source_not_contains`, `stderr_scan`, `file_exists`, `file_min_size`).
- Emit markdown verdict and JSON summary on the last line.
### Pattern 3: Verify registry safety before reset decisions
```bash
scripts/check_registry.sh <exp_name> [phase_root]
```
- Read registry entry for the experiment.
- Block reset recommendation for `RUNNING` experiments.
- Return status details and `safe_to_reset` decision JSON.
### Pattern 4: Show current registry health dashboard
```bash
scripts/status.sh [phase_root]
```
- Aggregate counts across active/completed sets.
- Show running experiments and execution location.
- Return compact JSON counters on the last line.
## Guidelines
- Always treat validation as fail-closed: any error-severity rule violation means gate failure.
- Always run `validate-experiment` before registry-facing actions.
- Never modify experiment source/config files during checks.
- Never execute reset/rerun from this skill; only report recommendations.
- Never override `RUNNING` experiments as safe to reset.
- Keep all operations read-only with respect to registry and experiment artifacts.
```skill-manifest
{
"schema_version": "2.0",
"id": "skill-system-gate",
"version": "1.0.0",
"capabilities": ["configurable-gate", "experiment-gate", "registry-safety", "experiment-status"],
"effects": ["fs.read", "db.read", "proc.exec"],
"operations": {
"validate-experiment": {
"description": "Validate experiment source artifacts and logs against gate_bank rules and return a pass/fail verdict.",
"input": {
"exp_name": { "type": "string", "required": true, "description": "Experiment directory name under experiments/" },
"phase_root": { "type": "string", "required": false, "description": "Phase directory path", "default": "/datas/store162/arthur0824hao/Study/GNN/FraudDetect/SubProject/Phase3" }
},
"output": {
"description": "Gate validation markdown plus machine-readable verdict.",
"fields": { "passed": "boolean", "errors": "number", "warnings": "number" }
},
"entrypoints": {
"unix": ["bash", "scripts/validate_exp.sh", "{exp_name}", "{phase_root}"]
}
},
"validate": {
"description": "Run configurable gate_rules.yaml checks and emit pass/fail with per-rule results.",
"input": {
"rules": { "type": "string", "required": false, "description": "Path to gate rules file", "default": "config/gate_rules.yaml" },
"artifact_root": { "type": "string", "required": false, "description": "Working directory for rule execution", "default": "." }
},
"output": {
"description": "Gate verdict with per-rule details.",
"fields": { "passed": "boolean", "errors": "number", "warnings": "number" }
},
"entrypoints": {
"unix": ["python3", "scripts/gate_validate.py", "--rules", "{rules}", "--artifact-root", "{artifact_root}"]
}
},
"verify-registry": {
"description": "Check registry state safety and recommend whether reset/rerun is safe without mutating state.",
"input": {
"exp_name": { "type": "string", "required": true, "description": "Experiment name in registry" },
"phase_root": { "type": "string", "required": false, "description": "Phase directory path", "default": "/datas/store162/arthur0824hao/Study/GNN/FraudDetect/SubProject/Phase3" }
},
"output": {
"description": "Registry safety markdown plus recommendation payload.",
"fields": { "found": "boolean", "status": "string", "safe_to_reset": "boolean" }
},
"entrypoints": {
"unix": ["bash", "scripts/check_registry.sh", "{exp_name}", "{phase_root}"]
}
},
"status": {
"description": "Show current registry dashboard with counts by status and running experiment details.",
"input": {
"phase_root": { "type": "string", "required": false, "description": "Phase directory path", "default": "/datas/store162/arthur0824hao/Study/GNN/FraudDetect/SubProject/Phase3" }
},
"output": {
"description": "Registry status dashboard and aggregate counters.",
"fields": { "running": "number", "needs_rerun": "number", "completed": "number", "total": "number" }
},
"entrypoints": {
"unix": ["bash", "scripts/status.sh", "{phase_root}"]
}
}
},
"stdout_contract": {
"last_line_json": true
}
}
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.