Skip to main content
redhat-et
GitHub-Creator-Profil

redhat-et

Repository-Ansicht von 94 gesammelten Skills in 14 GitHub-Repositories.

gesammelte Skills
94
Repositories
14
aktualisiert
17. Sept. 2026
Repository-Karte

Wo die Skills liegen

Top-Repositories nach gesammelter Skill-Anzahl, mit ihrem Anteil an diesem Creator-Katalog und ihrer Berufsverteilung.

#01
ripwire
19 Skills · 17. Sept. 2026
Klassifizierung ausstehend
20 %Anteil
#02
physical-ai-platform-intel
12 Skills · 9. Juli 2026
Marktforschungsanalysten und MarketingspezialistenSoftwareentwickler
2 Berufskategorien · 100 % klassifiziert
13 %Anteil
#03
rhdp-rca-plugin
10 Skills · 21. Juli 2026
Netzwerk- und ComputersystemadministratorenSoftwarequalitätssicherungsanalysten und -testerInformationssicherheitsanalystenSoftwareentwickler
4 Berufskategorien · 100 % klassifiziert
11 %Anteil
#04
ProtoBot
7 Skills · 14. Sept. 2026
Softwarequalitätssicherungsanalysten und -testerSoftwareentwickler
2 Berufskategorien · 43 % klassifiziert
7,4 %Anteil
#05
docsclaw
7 Skills · 23. Aug. 2026
AblagesachbearbeiterAllgemeine BürokräfteCompliance-BeauftragterKorrespondenzsachbearbeiterPersonalspezialistenSoftwareentwickler
7 Berufskategorien · 100 % klassifiziert
7,4 %Anteil
#06
physical-ai-skills
7 Skills · 4. Aug. 2026
SoftwareentwicklerDatenwissenschaftler
2 Berufskategorien · 100 % klassifiziert
7,4 %Anteil
#07
skillimage
6 Skills · 29. Apr. 2026
Korrektoren und TextmarkiererKundendienst-MitarbeiterLeitungssekretäre und Führungskräfte-AssistentenSekretäre und Verwaltungsassistenten (außer Rechts-, Medizin- und Führungsbereich)SoftwareentwicklerUnternehmensberater
6 Berufskategorien · 100 % klassifiziert
6,4 %Anteil
#08
gitops-manifest-validator
6 Skills · 16. März 2026
SoftwareentwicklerInformationssicherheitsanalystenNetzwerk- und Computersystemadministratoren
3 Berufskategorien · 100 % klassifiziert
6,4 %Anteil
Hier werden die Top 8 Repositories angezeigt; die vollständige Repository-Liste folgt darunter.
Repository-Explorer

Repositories und repräsentative Skills

ripwire-mcp
nicht klassifiziert

Wire ripwire into an agent as an MCP server — `ripwire wrap AGENT` (Claude Code, Cursor, Codex, Gemini…) — and choose the server verb mid-task. Also tool HEALTH: a symbol you expected is missing from the ranked output, the index feels stale after a rebase,…

17. Sept. 2026
ripwire-find-bug
nicht klassifiziert

You have a SYMPTOM — crash, exception, wrong output, failing test, error string — and don't know which code is responsible. Ranks candidates; a stack trace or sanitizer output maps onto frames innermost-first; 'it worked yesterday' / 'my last edit broke it' →…

14. Sept. 2026
ripwire-fresh-eyes
nicht klassifiziert

Maintenance risk in code you did NOT write — inheriting a module, planning a refactor, a suspected god object, 'what's gnarly / where's the rot / safe to touch?': hotspots, dead or inactive code, switches/defaults (--flags), clones, a function's real shape,…

14. Sept. 2026
ripwire-navigate
nicht klassifiziert

You can NAME the symbol: who calls it, what it calls, the path from A to B, its full body, or an exact literal/regex match. 'Safe to change or rename X — what breaks downstream?' = the transitive blast radius, not 1-hop callers. Three or more symbols →…

14. Sept. 2026
ripwire-orient
nicht klassifiziert

Landing COLD in an unfamiliar repo or subsystem, or about to open several files for one question: map first, read only what it ranks highest — main subsystems, entry points, 'how does X work / where is Y'. Also recover context after compaction, retrieve saved…

14. Sept. 2026
ripwire-security-scan
nicht klassifiziert

Security review: (1) vet an untrusted SKILL.md or .mcp.json BEFORE installing it — the injection/exfiltration scanner; CRITICAL blocks the install; (2) audit code on an untrusted-input path (a deserializer, parser, exec of user data, network endpoint): taint…

14. Sept. 2026
ripwire-change-check
nicht klassifiziert

Merge-SAFETY of an existing diff — yours before you push, or a PR you review: blast radius, tests to run, a broken contract (--edit-check=SYM), branch conflicts and landing order, unmerged work stranded on old branches, which ref defines it. Code QUALITY →…

13. Sept. 2026
ripwire-router
nicht klassifiziert

Start HERE when unsure which ripwire skill fits, or asked 'how do I use ripwire / where do I start'. A moment→skill map, cold start to handoff, plus the two reflexes that leak most: --exemplar before you write, --quality-delta before you call it done. One hop…

13. Sept. 2026
Es werden 8 von 19 gesammelten Skills angezeigt.
Es werden 8 von 12 gesammelten Skills angezeigt.
root-cause-analysis
Netzwerk- und Computersystemadministratoren

Perform root cause analysis and log analysis for failed jobs. Use when user wants to investigate job failures, analyze logs, find root causes, debug errors, troubleshoot infrastructure issues, or understand why a job failed. Investigate AAP job failures using…

21. Juli 2026
rca-annotator
Softwarequalitätssicherungsanalysten und -tester

Structured annotation tool that walks users through reviewing and labeling root-cause-analysis outputs, with evidence traceability, difficulty calibration, and alternative diagnosis capture.

13. Apr. 2026
feedback-capture
Softwarequalitätssicherungsanalysten und -tester

Ask user if they would like to provide feedback. Call scripts/formatting.py. Don't ask any follow up questions.

26. März 2026
root-cause-analysis
Informationssicherheitsanalysten

Perform root cause analysis and log analysis for failed jobs.Investigate AAP job failures using Splunk correlation and AgnosticD/AgnosticV configuration analysis. Correlates local Ansible/AAP job logs with Splunk OCP pod logs and retrieves relevant…

24. März 2026
root-cause-analysis
Netzwerk- und Computersystemadministratoren

Perform root cause analysis and log analysis for failed jobs. Investigate AAP job failures using Splunk correlation and AgnosticD/AgnosticV configuration analysis. Correlates local Ansible/AAP job logs with Splunk OCP pod logs and retrieves relevant…

24. März 2026
root-cause-analysis
Netzwerk- und Computersystemadministratoren

Perform root cause analysis and log analysis for failed jobs. Use when user wants to investigate job failures, analyze logs, find root causes, debug errors, troubleshoot infrastructure issues, or understand why a job failed. Investigate AAP job failures using…

24. März 2026
incident-investigator
Netzwerk- und Computersystemadministratoren

End-to-end incident investigation workflow that fetches logs and performs root cause analysis. Use when a user wants to investigate incidents, analyze job failures, fetch and analyze logs in one workflow, or debug infrastructure issues. Combines log-fetcher,…

17. März 2026
context-fetcher
Netzwerk- und Computersystemadministratoren

Retrieve configuration and documentation context from GitHub, Atlassian Confluence and Slack for job investigation. Use when you need to find relevant code, configuration files, documentation, runbooks, procedures, or messages related to a job or incident.…

17. März 2026
Es werden 8 von 10 gesammelten Skills angezeigt.
board-tidy
nicht klassifiziert

Maintain a GitHub project board by moving unblocked issues to Ready and flagging stale statuses. Use when asked to tidy, reconcile, or review a GitHub project board.

14. Sept. 2026
issue-audit
nicht klassifiziert

Audit open GitHub issues and PRs against the repository to find missing tasks, implementation gaps, and issues that need breaking down. Use for issue-tracker audits or milestone gap analysis.

14. Sept. 2026
issue-sync
nicht klassifiziert

Synchronize a GitHub issue tracker with the implementation plan by proposing missing issues, blocking relationships, issue comments, and tracking-issue updates. Use when asked to create or refresh project issues. Always run `issue-audit` first.

14. Sept. 2026
eliciting-requirements
nicht klassifiziert

Turns goals, feature requests, interface descriptions, existing requirements, and requirement sets into precise, implementation-independent EARS requirements with focused questions, supporting suggestions, complete verification contracts, and consistency…

11. Sept. 2026
pull-request
Softwarequalitätssicherungsanalysten und -tester

Provides a structured process for creating pull requests use when asked to "make a PR".

9. Sept. 2026
review-pr
Softwarequalitätssicherungsanalysten und -tester

Provides a structured process and a comment format for reviewing pull requests. Use when asked to "review a PR", "review PR #N", or "give me a review".

8. Sept. 2026
rebase-pr
Softwareentwickler

Provides a structured process for rebasing pull requests use when asked to "rebase a PR".

31. Aug. 2026
datasets
Datenwissenschaftler

Use when inspecting, validating, or pulling a user-supplied dataset for fine-tuning or general use, or when asked what data a robot-policy model (pi0.5, DreamZero) was trained or fine-tuned on.

4. Aug. 2026
deploy-checkpoint
Softwareentwickler

Use when standing up a finished fine-tuning checkpoint as a live model endpoint for testing or comparison against the base model.

4. Aug. 2026
deploy-model
Softwareentwickler

Use when sizing hardware or drafting manifests for a model that fits an existing runtime pattern (stock vLLM chat, or vLLM-Omni multimodal). For a model needing a runtime this platform hasn't run before, use new-model-runtime instead.

4. Aug. 2026
fine-tuning
Softwareentwickler

Use when discussing, submitting, or checking on a fine-tuning run — GPU training jobs on pi05/robot-policy checkpoints, submit_finetune_run, get_finetune_run_status, or questions like "how's my fine-tune doing" or "kick off training on X dataset."

4. Aug. 2026
model-specs
Softwareentwickler

Use when asked about a catalog model's own static characteristics — architecture, dataset/training compatibility, serving runtime requirements — e.g. "what was DreamZero trained on" or "does pi0.5 need a fixed camera count." Not for live status, scaling, or…

4. Aug. 2026
models
Softwareentwickler

Use when listing deployed models, checking a specific model's status/output_kind, scaling it up/down, tearing down a checkpoint deployment, or permanently removing a catalog model.

4. Aug. 2026
new-model-runtime
Softwareentwickler

Use when onboarding a model whose serving runtime this platform hasn't run before (not stock vLLM chat or vLLM-Omni) — its own native server/CLI, not something generate_model_manifests can template. See also the deploy-model skill for models that DO fit an…

3. Aug. 2026
analyzing-kubernetes-security-posture
Informationssicherheitsanalysten

Analyzes Kubernetes manifests for security posture, threat modeling, and attack path identification. Use when reviewing manifests for security risks beyond simple lint checks. This skill identifies compound vulnerabilities where multiple misconfigurations…

16. März 2026
k8s-lint-validator
Softwareentwickler

Runs comprehensive Kubernetes manifest linting with kube-linter, kubeconform, and pluto. This skill should be used when the user wants to validate K8s manifests. Validations can include best practices, schema correctness, deprecated APIs, and security issues.…

16. März 2026
mapping-kubernetes-compliance-controls
Informationssicherheitsanalysten

Use when validating Kubernetes manifests against compliance frameworks (CIS Kubernetes Benchmark, Pod Security Standards, PCI-DSS, HIPAA, SOC2, NIST). Use when generating compliance reports, audit evidence, or mapping controls to regulatory requirements. Use…

16. März 2026
reasoning-about-kubernetes-cost-reliability
Netzwerk- und Computersystemadministratoren

Use when reviewing Kubernetes manifests for resource cost implications, overprovisioning waste, reliability gaps (single replica, no PDB, missing anti-affinity), or cost-vs-reliability tradeoff decisions. Use when someone asks "how much does this cost?" or…

16. März 2026
validating-cross-resource-consistency
Softwareentwickler

Use when reviewing, creating, or modifying Kubernetes manifests that contain multiple resources. Use when Services, Deployments, ConfigMaps, Secrets, RBAC resources, Ingress, Routes, or NetworkPolicies appear together. Use when manifests reference other…

16. März 2026
validating-kubernetes-intent-and-architecture
Softwareentwickler

Use when reviewing Kubernetes manifests to validate design intent and architectural decisions. Use when manifests contain unexplained port exposure, single-replica production deployments, multi-container Pods, unusual update strategies, or any configuration…

16. März 2026
12 von 14 Repositories angezeigt