By danielscholl
OSDU platform operations — agents, skills, and live platform access for analytics, QA testing, builds, knowledge management, and shipping across OSDU Community Implementation environments on Azure
Clone OSDU GitLab repositories to the local workspace with optional worktree layout.
Prime understanding of the OSDU workspace -- discover cloned repos, available tools, plugin capabilities, and current context. Quick, low-token overview.
Run QA tests, analyze failures, compare environments, or generate QA reports for OSDU platform services.
Ship local changes -- review, commit, push, and create a merge/pull request.
Execute build and test commands for OSDU Maven projects and return structured summaries. Use proactively when the user asks to build, compile, or run Maven verify on an OSDU service. Not for test execution against live environments (use qa-runner) or code analysis.
Orchestrator for OSDU (Open Subsurface Data Universe) platform operations including CI/CD pipelines, test reliability, contributions, GitLab operations, and live platform access. Use proactively for queries about pipeline status, test pass rates, flaky tests, open MRs, contributor rankings, OSDU service metrics, or live platform data (records, schemas, entitlements). Not for cimpl-azure IaC work -- that belongs to the cimpl agent.
Analyze OSDU test failures and identify root causes with deep OSDU platform expertise. Use proactively when tests have failed and need diagnosis, when investigating service issues, or when the user asks why tests are failing. Not for running tests (use qa-runner) or comparing environments (use qa-comparator).
Compare OSDU test results across multiple environments to identify regressions and improvements. Use proactively when validating feature branches, comparing staging to production, detecting regressions, or when the user asks to diff or compare environments. Not for running tests (use qa-runner) or analyzing individual failures (use qa-analyzer).
Generate professional QA reports from OSDU test results in HTML and Markdown formats. Use proactively after tests have been run to create dashboards, reports, or executive summaries. Not for running tests (use qa-runner) or analyzing failures (use qa-analyzer).
Run Java acceptance or integration tests from an OSDU service repository against a live deployed environment. Resolves environment configuration, auth credentials, and SSL truststore automatically. Use when the user says 'run acceptance tests for partition', 'test the storage service against my environment', 'execute integration tests for legal', or 'verify partition with acceptance tests'. Not for: test reliability analysis (use osdu-quality), building services (use build-runner), checking environment health (use health), or unit tests without a live service.
Use when reading from, writing to, or organizing the OSDU brain Obsidian vault — the project's long-term memory and knowledge base. Trigger this skill whenever the user mentions the vault, brain, daily notes, daily briefing, reports, knowledge base, decision records, incident reports, dependency reports, QA reports, meeting notes, architecture notes, or asks to "remember", "store", "log", or "write up" anything related to project operations. Also trigger when generating MR summaries, pipeline analysis, RCA write-ups, dependency audits, or any content destined for the brain vault. Use when the user says "vault", "brain", "daily note", "remember this", "store this", "log this", "write up", or references knowledge base operations. Not for: ad-hoc chat answers, one-time commands, or information already in git history.
Generate daily OSDU briefing notes by aggregating GitLab MRs, SPI fork health, vault goals, and brain knowledge into an insightful daily note. Use when the user says "gm", "good morning", "briefing", "daily briefing", "morning standup", "what's on my plate", or "start my day". Not for: ad-hoc status checks or single-service queries.
Execute build/test commands and return structured summaries. Use for Maven, Node, or Python builds during dependency remediation. Use when the user says "build", "compile", "test", "verify", "run tests", "maven verify", "unit tests", or "build summary". Not for: deployment, CI/CD pipeline management, or code generation.
Clone OSDU GitLab repositories and infrastructure repos to the workspace. Supports single service, category, or all repos with bare-clone worktree or standard git clone. Use when the user asks to clone an OSDU repo, set up the workspace, download source code for a service, or clone infrastructure repos. Not for: building or testing cloned repos (use maven or acceptance-test), or checking repo status (use glab or osdu-activity).
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code marketplace that bundles specialized agents, skills, and live platform access into two installable plugins for infrastructure automation, platform analytics, QA testing, and knowledge management across OSDU Community Implementation environments on Azure.
Built for OSDU maintainers, platform engineers, QA contributors, and community operators.
| Plugin | Components | What you use it for |
|---|---|---|
| osdu | osdu:osdu agent, 21 skills | Builds, dependencies, MRs, tests, live platform queries, knowledge management |
| cimpl | cimpl:cimpl agent, 3 skills | Terraform, Helm, AKS, debugging, verification |
Requires Claude Code.
/plugin marketplace add danielscholl/claude-osdu
/plugin install osdu@claude-osdu
/plugin install cimpl@claude-osdu
/reload-plugins
> give me a morning briefing
> clone partition
> what pipelines are failing across OSDU?
> check the health of my environment
> run acceptance tests for partition
> review MR !845
> ship it
Platform operations across 30+ OSDU GitLab services.
| Category | Skills |
|---|---|
| Knowledge | brain, briefing, learn, consolidate |
| Analytics | osdu-activity, osdu-engagement, osdu-quality |
| Build & Deps | maven, dependency-scan, build-runner, remediate |
| QA Testing | osdu-qa, acceptance-test |
| Git Workflow | send, mr-review, contribute, glab, fossa, maintainer |
| Workspace | clone, setup |
Agents: osdu:osdu (orchestrator), osdu:build-runner, osdu:qa-runner, osdu:qa-analyzer, osdu:qa-comparator, osdu:qa-reporter
MCP Server: osdu-mcp-server for live platform access (31 tools across search, storage, schema, entitlements, legal, partition)
Azure infrastructure automation for OSDU Community Implementation deployments.
| Category | Skills |
|---|---|
| Infrastructure | iac, health, setup |
Agent: cimpl:cimpl (infrastructure specialist)
Uses the skilltest four-layer test framework.
make test # L1 + L2 + pytest (fast)
make lint # L1: Structure validation
make unit # L2: Trigger eval dry-run
make integration P=osdu # L3: Multi-turn session tests
make benchmark P=osdu S=brain # L4: Skill value comparison
make report # Test inventory
See CONTRIBUTING.md.
npx claudepluginhub danielscholl/claude-osdu --plugin osduDOCX creation, editing, and redlining with tracked changes and OOXML validation
Four-layer test framework for Claude Code plugin skills — structure validation, trigger accuracy, session testing, and skill value comparison
Software development lifecycle automation - slash commands, agents, and GitHub/GitLab webhook watchers
Branded presentation and carousel generation with brand voice system
Gas Town SDLC — brief → design → plan pipeline that turns ideas into Gas Town beads (bd create commands + dependency graph)
Skill evaluation and benchmarking - test skill effectiveness with behavioral eval cases, grade results, and track quality improvements
Platform engineering agents providing expertise in developer platforms, IaC, and tooling
Practical guidance for platform engineers across Claude, Codex, Cursor, and Copilot: Kubernetes, Kyverno, Helm, Terraform, Flux CD (Flux Operator, FluxInstance, gitless OCI delivery, cluster debug, repo audit), Argo CD, GitHub Actions (composite actions, SHA pinning, OIDC, 11 production examples), AWS (CloudFront, WAF, Lambda@Edge, IAM, IRSA), Azure (AKS workload identity), GKE (Workload Identity Federation), Linkerd, Linux, networking, MCP development, observability, SOC 2 compliance, PR review, PR triage, KEDA autoscaling, Karpenter node autoscaling, supply chain security (Cosign, SBOM, SLSA), Falco runtime security, Chaos Engineering, DORA Metrics, LLM Observability (Datadog LLMObs), and animated docs. Every answer includes blast radius, validation steps, and rollback plan.
No description provided.
Multi-agent orchestrator for Claude Code. Track work with convoys, sling to polecats. The Cognition Engine for AI-powered software factories.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development