singularity

Runs a bounded recursive improvement cycle over agent instructions and the news crawler codebase.

1|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/metabench/copilot-dl-news --skill singularity-metabench
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: singularity
Source: https://github.com/metabench/copilot-dl-news/tree/main/.claude/skills/singularity
Command: npx skills add https://github.com/metabench/copilot-dl-news --skill singularity-metabench

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent workflows and crawler code improve ad hoc without verification, so gains are unmeasured and scaffold instructions rot. This Skill runs one structured cycle that improves both the agent's own instructions (skills, memory, tests, prompts) and the copilot-dl-news crawler plus jsgui3 UI, with every change gated by verification and measurable metrics. ## Core Features & Use Cases - Dual-track cycle: Each invocation picks one Track A improvement (codifying procedures as skills, memory, or tests) and one Track B improvement (crawler engine or jsgui3 UI work), then verifies and commits both. - Adversarial quality gate: Forces skeptic-mode self-critique against explicit product and instruction rubrics before shipping, countering the model's bias to overrate its own work. - Falsifiable recursion metrics: Tracks cost-per-improvement, second-order tool creation, rubric pass rates, and raw-SQL reduction to prove whether the loop is actually compounding. - Model-swap calibration: Maintains a lineage table and re-probes empirical heuristics when the underlying model changes, banking portable artifacts across model generations. - Use Case: A maintainer invokes the skill to run one cycle: it orients via git status and memory files, improves a verification harness (Track A), fixes a crawl telemetry UI panel in jsgui3 (Track B), screenshots and tests both, commits in small chunks, and records the deltas in LOOP_STATE. ## Quick Start Invoke the singularity skill to run one improvement cycle over the agent instructions and the news crawler codebase.

Frequently Asked Questions about singularity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run one recursive improvement cycle with this skill?▼

Invoke the skill once per cycle. It orients via git status and memory files, picks one instruction improvement and one crawler or UI improvement, applies an adversarial quality gate, verifies with screenshot and end-to-end harnesses, then commits and records both deltas.

What can the agent autonomously change when running this loop?▼

The agent may create, revise, or retire its own skills, memory files, verification harnesses, docs, and continuation prompts, each versioned and justified by measurable gain. It may not edit owner hard rules, safety invariants, verification gates, or the never-git-add list.

How does the skill verify crawler and UI changes are high quality?▼

Verification uses a ui-screenshot harness read as a user, real NewsDatabase end-to-end tests for logic, adversarial multi-lens review for correctness-sensitive changes, and the project's normal test suite. Work ships only when the strongest self-critique finds no real defect.

Does this skill perform unbounded self-improvement or modify model weights?▼

No. It is a bounded, verification-gated loop at the agent-system level covering scaffold artifacts like skills, memory, and tests. It explicitly does not edit model weights, does not relax its own constraints, and requires a measurable delta per cycle.

What happens when the underlying model changes between cycles?▼

On a detected model swap, the skill appends a row to the lineage table in docs/agi/SELF_MODEL.md and recalibrates: owner rules carry unconditionally, empirical heuristics get re-probed before trust, and model-specific behavioral compensations are re-tested or retired.

How is compounding improvement measured rather than asserted?▼

The skill tracks cost-per-improvement trend, count of second-order tools produced, rubric first-pass rate, defects caught pre-ship versus post-ship, and live raw-SQL sites in the coordination repo. Flattening returns trigger a shift toward portable artifacts for successor models.