Individual skill
self_attempt_01
Not available
experiments/claude_code_glm_5_2_max/reports/skills/task_group_004/self/self_attempt_01/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
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
SKILL.mdcore · 28,855 bytes
Read excerpt
# apex-retention-ops — ApexCloud Retention Operations SOP
Executable skill for CRM retention-analytics tasks against the ApexCloud
Retention Operations API. Covers five task archetypes: renewal risk queue,
QBR metrics packet, receivables + pipeline operations review, churn model
validation + outreach ranking, and the high-touch retention operations board.
All conventions below were reverse-engineered from the live API schemas and
the train answer templates (self-evolution: no gold answers were used). Where
an exact policy value could not be confirmed, the field name + governing rule
are stated so a solver applies the right policy.
---
## 0. Environment