Individual skill
ce-pov
Judge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach set. Use for an oracle panel to consult other models and reconcile their opinions. Use ce-explain for understanding and ce-doc-review for findings review.
skills/ce-pov/SKILL.md
Source commit 263498844fc024596db21110198d8222b1c98478
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 8, 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.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 25,972
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- compound Repository topic
- engineering Repository topic
- engineering Derived category
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 · 7,805 bytesSKILL.mdcore · 7,805 bytesreferences/agents/external-evidence-researcher.mddoc · 2,594 bytesreferences/agents/pov-peer.mddoc · 2,584 bytesreferences/agents/precedent-activity-scout.mddoc · 2,875 bytesreferences/agents/project-grounding-scout.mddoc · 4,519 bytesreferences/boundaries.mddoc · 3,695 bytesreferences/cross-model-panel.mddoc · 37,145 bytesreferences/followup.mddoc · 1,361 bytesreferences/grounding.mddoc · 7,701 bytesreferences/intake.mddoc · 6,229 bytesreferences/invocation.mddoc · 4,861 bytesreferences/method.mddoc · 8,689 bytesreferences/pov-schema.jsonasset · 1,947 bytesreferences/report.mddoc · 1,156 bytesscripts/cross-model-pov.shruns · 56,497 bytesscripts/peer-job-runner.pyruns · 109,274 bytes
Read excerpt
# Form a Point of View
Produce a decisive, project-grounded point of view in the subject's own shape: a **graded verdict** on an external-adoption question, a **holistic take** on a document, or a **position** on a supplied approach set. The subject is whatever this skill was invoked with, in the prompt or the conversation. Stay read-only while forming and reconciling the POV. You are done when the POV is delivered with its attribution and required disclosure, or when an explicit blocker is returned. Use `ce-bakeoff` to develop competing solutions, `ce-ideate` to explore opportunities, or `ce-brainstorm` to establish goals.
## Grounding is not optional
**Never issue a POV you did not earn against the project's own context.** Every subject must meet the minimum project evidence (the **project floor**) in `references/method.md`. An external-adoption verdict must also meet the full external evidence bar there. A document or approach-set POV must verify against outside sources any external claim its bottom line depends on. Nothing the conversation asserts substitutes for grounding.
## Consumer and interaction
Deliver a supported position in the form the intended consumer can use. Lead with the decision and preserve the evidence, material tradeoffs, uncertainty, and conditions that determine it. Make identifiers understandable without requiring the reader to reopen the subject. In progress updates, say in plain words what you are checking and which model or helper is checking it. Never name this skill's machinery there (payloads, scouts, dossiers, tiers, round numbers, scratch files).
When contributing to an ongoing workflow, return the result and leave continuation to its owner, the calling workflow. Do not add follow-up or panel offers to that return. An explicit oracle or named-peer request still runs the panel, including when it comes from a calling workflow.