ai-oc-glm51

Route engineering tasks through ACG workflows and GLM-5 via z.ai.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/EndUser123/cc-marketplace --skill ai-oc-glm51
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-oc-glm51
Source: https://github.com/EndUser123/cc-marketplace/tree/main/plugins/cc-skills-ai-cli/skills/ai-oc-glm51
Command: npx skills add https://github.com/EndUser123/cc-marketplace --skill ai-oc-glm51

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode-powered assistant that grounds research and engineering analysis by routing tasks through an ACG-style workflow and GLM-5 model via z.ai.

Core Features & Use Cases

  • Soft triage of tasks into RESEARCH, ENGINEERING, DESIGN, or RCA with user override.
  • Deterministic routing to ACG, TDD, Adversarial Review, or Hypothesis Ledger based on triage.
  • Verification pyramid for ENGINEERING path (Tier 1 Unit, Tier 2 Integration, Tier 3 E2E) and source-fidelity citations.
  • Handles end-to-end analysis from problem framing to final output with archival references.

Quick Start

Provide a task prompt like 'Analyze the auth module and propose improvements' to trigger the ACG workflow and routing.

Frequently Asked Questions about ai-oc-glm51

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

FAQPage Schema
How do I route engineering analysis tasks through an ACG workflow with GLM-5?

To route engineering analysis tasks through an ACG workflow with GLM-5, provide a task prompt to trigger soft triage into RESEARCH, ENGINEERING, DESIGN, or RCA, which then deterministically routes to the appropriate workflow via z.ai.

Can I use OpenCode to perform root-cause investigations and design decisions?

OpenCode can perform root-cause investigations and design decisions by grounding analysis in source material and routing prompts through the ACG workflow and GLM-5 model to deliver structured outputs with source-fidelity citations.

What is the best way to triage codebase tasks into research or engineering paths?

The best way to triage codebase tasks into research or engineering paths is using soft triage to categorize prompts into RESEARCH, ENGINEERING, DESIGN, or RCA, with user override options for deterministic routing.

Does the engineering path support automated verification for unit and integration tests?

The engineering path supports automated verification through a verification pyramid that includes Tier 1 Unit, Tier 2 Integration, and Tier 3 E2E testing, ensuring source fidelity and structured outputs.

How do I override the default triage routing for a design analysis task?

To override the default triage routing for a design analysis task, use the user override feature during the soft triage phase to manually select DESIGN, redirecting the prompt to the Hypothesis Ledger or appropriate workflow.

What are the limitations of using ACG workflows for codebase analysis?

ACG workflows for codebase analysis enforce strict source fidelity and frontmatter-defined processes, limiting outputs to structured formats and explicit path choices, which may restrict freeform exploratory coding tasks.