cxas-cuj-report-generator

cxas-cuj-report-generator is a skill for Claude Code, Codex from GoogleCloudPlatform/cxas-scrapi. It costs 51 tokens per session (2,868 once invoked), scanned A, original, Apache-2.0.

A tool for turning customer requirement files—such as diagrams, business requirement documents, and code—into conversation transcripts and interactive Critical User Journey reports. A Critical User Journey describes an important path a user takes through a product or service.

In plain words
What is it for?
Use it to extract dialogue from requirement files, organize user scenarios, and compile interactive reports for reviewing customer journeys.
Why use it?
It brings scattered requirements into one structured view and helps preserve coverage while the material is being analyzed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

Good fit Use it to extract dialogue from requirement files, organize user scenarios, and compile interactive reports for reviewing customer journeys.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add GoogleCloudPlatform/cxas-scrapi --skill cxas-cuj-report-generator
Clone the repo
git clone --depth 1 https://github.com/GoogleCloudPlatform/cxas-scrapi

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cxas-cuj-report-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator/github.svg)](https://agentmods.dev/skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator)
Your own site
<a href="https://agentmods.dev/skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cxas-cuj-report-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/cxas-scrapi/cxas-cuj-report-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,868 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.02868
Opus 5 $0.00026 $0.01434
Sonnet 5 $0.00010 $0.00574
Haiku 4.5 $0.00005 $0.00287

Measured 10d ago against content hash 29cc9caada8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

cxas-cuj-report-generator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

The scan reads SKILL.md. This mod also ships 19 executable files (append_turn.py, compile_deliverables.py, construct_report.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/cxas-cuj-report-generator/SKILL.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Critical User Journey (CUJ) Transcript & Report Generator Skill

Use this skill when asked to extract dialogue transcripts or compile interactive Critical User Journey (CUJ) reports from a directory of customer requirement documents (such as diagrams, BRDs, code etc.).

Core Protocols

To ensure 100% coverage and zero data loss, you MUST follow these core rules:

  • Robust Extraction: Follow the protocol defined in the cxas-protocol-robust-extraction skill.
  • Two-Phase Ingestion: Follow the protocol defined in the cxas-protocol-two-phase-ingestion sub-protocol inside protocols/cxas-protocol-two-phase-ingestion/.
  • Checklist Mandate: The orchestrator and all subagents MUST follow the agent-protocol-checklist protocol to maintain a local task_checklist.json file, ensuring they track their progress and not lose coverage during execution.
  • Orchestrator Delivery Assurance: The orchestrator MUST act as a strict, independent Delivery Auditor. BEFORE closing subagents, terminating the watchdog, or reporting campaign success to the user, the orchestrator MUST physically verify the existence, size bounds, and schema compliance of all registered deliverables (specifically gecx_customer_report.html and gecx_cuj_report.html) on disk. Under no circumstances may the orchestrator assume completion without executing a physical file-presence check.
  • Auditing: The orchestrator MUST periodically check the subagent's scratch directory to ensure the task_checklist.json file is being created and maintained. If the file is missing or not updated, the orchestrator MUST terminate the subagent and respawn it with stronger enforcement instructions.

Core Workflow Steps

Follow this 5-step structured workflow to execute the task:

  1. Scoping & Type Discovery: Prepare the environment and identify required skills.

    • Access Files: Ensure you have access to the source artifacts in your local workspace.
      • Tip (Drive Links): If the source is a Google Drive link or folder ID, you MUST use the gdrive skill to access them.
    • Detect Inventory Types: To identify framework signatures and map them to correct Ingestors, you MUST use the framework detector agent defined in agents/framework_detector.md. Using this agent, scan the input files to inventory all file extensions and detect potential frameworks. Spawn parallel Framework Detector subagents to scan partitions of the file tree.
    • Map Ingestors: Use the scoping report generated by the Framework Detector to select or create the correct specialized skills in ingestors/frameworks/ or ingestors/files/.

Read the full file on GitHub · 236 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 236 lines · 51 tokens per session scan A 29cc9caada8d

Subscribe to this mod's changes

cxas-cuj-report-generator is a skill published in the GitHub repository GoogleCloudPlatform/cxas-scrapi (96 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 2,868 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens