Menu

Individual skill

reflect-3_attempt_01

0upvotes

Not available

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_004/reflect-3/reflect-3_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# SKILL: ApexCloud Retention Operations — CRM Analytics SOP

A reusable procedure for solving ApexCloud Retention Operations analytics tasks
(renewal-risk queues, QBR metric packets, receivables/pipeline reviews, churn
validation/ranking, and high-touch retention boards). Every task gives you one
prompt plus an `answer_template.json`; your job is to fill every template field
exactly, with the right values, precision, enum strings, and controlled
`policy_codes`. This file captures the company's standard conventions for each.

---

## 1. Data access (the remote API is the ONLY source of truth)

Use the ApexCloud Retention Operations HTTP API. A prompt may name a localhost
URL or an `env/setup.sh`; ignore that and use the live base URL configured for
Back to top