
Use when the user wants to evaluate engineering assessments (take-homes, live coding, system design) with structured rubrics and avoid over-indexing on trivia or memorization.
Use when the user wants to assess engineering team skills, build a skills matrix, identify gaps vs. roadmap, and design training or hiring plans.
Use when the user wants to diagnose engineering performance issues (individual or team), distinguish systemic vs. individual patterns, and design data-driven interventions.
Use when the user is planning an exit or handoff for a departing team member; produce exit checklist (access, docs, knowledge transfer, last day), handoff doc, and access-revoke list.
Use when the user is preparing for a 1:1 meeting and wants an agenda from recent feedback, incidents, goals, and prior notes, with talking points and follow-ups.
Use when designing or reviewing org structure, team topology, headcount plans, spans and layers, operating models, role ownership, capacity, and decision rights.
Use when building people analytics reports, HR dashboards, headcount reports, attrition summaries, hiring funnel reports, onboarding health reports, or executive people briefings.
Use when an AI agent should use the Clous CLI to inspect objects, run agents, retrieve knowledge, or manage webhooks in noninteractive JSON workflows.
Use when HR work involves legal risk, employment policy, PIPs, termination, accommodations, compensation, leave, investigations, employee relations, jurisdiction constraints, or legal-review preparation.
Use when an AI agent can call Clous remote MCP tools to inspect or operate the Clous platform, HR, or employee surfaces.
Use when reading, creating, updating, or deleting Clous objects such as employees, candidates, jobs, reviews, skills, and forms.
Use when the user wants to create or refine an engineering career path, define level expectations, or design promotion criteria and packets.
Use when building or reviewing direct Clous API v1 integrations, including responses, object CRUD, API keys, webhooks, tool endpoints, retries, pagination, and structured error handling.
Use when wiring, testing, or documenting Clous command-line integration for developers or AI agents, including noninteractive JSON mode and profile/env configuration.
Use when the user wants to evaluate engineering assessments (take-homes, live coding, system design) with structured rubrics and avoid over-indexing on trivia or memorization.
Use when implementing Clous OAuth 2.1 or OIDC clients, including PKCE, discovery, protected-resource metadata, token exchange, refresh, and userinfo.
Use when configuring, testing, or implementing remote Clous MCP server integrations for Codex, Claude, Cursor, ChatGPT, or other MCP clients.
Use when modifying, validating, or preparing releases for the Clous Python and TypeScript SDKs bundled in this plugin.
Use when integrating external agents with Clous A2A endpoints, including manifest discovery, run creation, status polling, streaming URLs, HMAC signatures, scopes, and allowlists.
Use when the user wants to create or refine 30/60/90 day onboarding plans for new engineering hires, with clear milestones, stakeholders, and risk mitigation.
Use when creating, inspecting, waiting for, or summarizing Clous agent runs through `/v1/responses` or A2A run endpoints.
Use when an AI agent needs to inspect, create, update, delete, or troubleshoot Clous webhook subscriptions and events.
Use when an AI agent should call Clous API v1 directly through the SDK or HTTP to manage objects, agent runs, webhooks, and tool retrieval.
Use when planning, communicating, or diagnosing organizational change such as restructures, process changes, new operating models, policy rollouts, system migrations, or adoption programs.
Use when implementing Clous webhook subscriptions, event discovery, receiver validation, signature verification, retries, and idempotent processing.
Use when the user wants to start or refine an engineering hiring process and needs a structured, legally-aware intake document for a new or replacement role.
Use when the user wants to detect or assess engineering burnout risk (after-hours work, on-call load, unsustainable pace, team health checks) for an individual or team.
Use when the user wants to detect or assess engineering burnout risk (after-hours work, on-call load, unsustainable pace, team health checks) for an individual or team.
Use when the user wants to create or refine an engineering career ladder, define level expectations, or design promotion criteria and packets.
Use when the user is planning an exit or handoff for a departing team member; produce exit checklist (access, docs, knowledge transfer, last day), handoff doc, and access-revoke list.
Use when the user wants to diagnose engineering performance issues (individual or team), distinguish systemic vs. individual patterns, and design data-driven interventions.
Command and skill mapping for the clous-hreng plugin; use when deciding which /clous command or skill to use for hiring, performance, onboarding, burnout, skills, ladder, 1:1, or offboard.
Use when the user is preparing for a 1:1 meeting and wants an agenda from recent feedback, incidents, goals, and prior notes, with talking points and follow-ups.
Use when the user wants to start or refine an engineering hiring process and needs a structured, legally-aware intake document for a new or replacement role.
Use when the user wants to create or refine 30/60/90 day onboarding plans for new engineering hires, with clear milestones, stakeholders, and risk mitigation.
Use when the user wants to assess engineering team skills, build a skills matrix, identify gaps vs. roadmap, and design training or hiring plans.
Use when an external AI agent needs to operate Clous safely across MCP, SDK, CLI, and API surfaces while preserving user/company context and avoiding unsafe mutations.
Use when retrieving Clous HR knowledge, support docs, or system log context through Clous tool endpoints or MCP resources.