Drop the dedicated-repo publish path. Restore GitHub Actions Pages
deploy on Agent-Skills-for-Context-Engineering while keeping the
on-page Long-Horizon Prompting brand.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Rebrand the project site identity and public Pages path to
long-horizon-prompting. Publish via a dedicated Pages repo so the
URL matches the project instead of Agent-Skills-for-Context-Engineering.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Surface author credit on the overview byline and shared page footers,
linking to muratcankoylan.com and x.com/koylanai.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Add deterministic HTML/metadata/link/reference/sitemap validation, exact rubric drift checks against the authoritative skill template, generated-file drift checks including untracked artifacts, and Puppeteer production tests under the real GitHub Pages base path. Test five pages across four viewport widths, clipboard controls, keyboard tabs, full prompt visibility, downloads, and no-JS fallbacks. Pin Pages workflow actions, split read-only build from privileged deployment, pin the skill install to a full commit, and commit the npm lockfile.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Reframe the project around the skill rather than the CDC case: add static Overview, Guide, Prompt Lab, References, and 404 pages; a copyable rubric-complete brief template; prompt/harness boundaries; gotchas and workflow; 33 caveated research/vendor references; eight generated prompt downloads; shared navigation and copy controls; accessible tab semantics; responsive editorial styling; and updated release screenshots. The CDC run is now explicitly one unreviewed case study, not the site's foundation.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Turn the static comparison into a release site: full-height prompts on the website, capture-only bounded panes for PNGs, copy controls for every prompt and the Cursor install command, direct GitHub skill/repository/provenance links, a concise technical release explanation, responsive layout, social metadata, and an Actions-based Pages deployment. GitHub Pages still needs the one-time repository setting switched to GitHub Actions after merge.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Collapse soft-wrapped source newlines into flowing paragraphs for display, keep section headers and lists intact, widen the lab layout, and recapture under shot-* paths so stale prematurely wrapped previews cannot linger.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Rewrite all four right-side artifacts as copy-ready launch prompts generated with the long-horizon-prompting method. Remove every placeholder and add concrete success predicates, named non-solutions, evidence contracts, domain-specific audits, return gates, and harness boundaries. Fresh reviewers closed evaluation-leakage, production-signature, theorem-model, and security-scope defects. The UI now presents readable fixed-height prompt panes with word counts and Copy actions. Rename screenshots to optimized-* paths to prevent stale prompt previews.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Move every redesigned PNG to a new editorial-* path, remove the superseded screenshot paths, update the README preview, and make the capture script emit only the cache-safe names. This prevents GitHub and Cursor from serving the old navy dashboard by URL.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Replace the dark gradient dashboard, neon score cards, pill labels, and rounded panels with a restrained warm-paper system: serif display typography, black rules, generous whitespace, one muted accent, document-like prompt columns, and a methods-table scorecard. Simplify labels and recapture all 13 PNGs. The new assets are also about 1.2 MB smaller.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Lab README covers the four use cases, the reproduce steps (fetch -> verify ->
install -> build -> capture), how to read the scorecard, and an explicit
honesty/limits section (skill's own rubric, per-pair residual risk, unreviewed
CDC proof). Add the example to the root README examples table.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Generated by scripts/capture.mjs. Money-shot crops (hero, *-split, *-scorecard)
rendered at 2x for legible prompt text; *-full overview pages at 1x to keep the
committed set light (~6MB total).
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
build_lab.py is the single source of truth: it defines the skill's 10-dimension
pre-launch rubric and four before/after prompt pairs (ML model-improvement run,
parallel approximation-ratio proof, distributed-systems RCA, security audit),
scores both versions, and emits data/prompt-pairs.json and ui/data.js.
The 'before' prompts are competent prompt-engineered launch prompts (persona,
context, chain-of-thought, explicit format, persistence); the 'after' briefs are
the skill's pseudo-formal task brief applied to each. Each pair records a residual
risk the brief cannot remove, and the UI carries an explicit honesty note that the
rubric is the skill's own. Aggregate rubric score moves 11% -> 100% across the four.
The UI is dependency-free and file:// safe (loads window.PROMPT_LAB_DATA from
data.js); capture.mjs drives system Chrome via puppeteer-core to render it.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
.cursor/ is gitignored (project-local IDE state), so install_skill.sh is the
committed record of the Cursor install: it copies the skill directory into
.cursor/skills/ and validates the installed copy with the reference agentskills
CLI. Verified locally with skills-ref 0.1.1 (Valid skill).
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Fetch OpenAI's published GPT-5.6 Sol Ultra Cycle Double Cover prompt and
candidate proof (the exemplar the long-horizon-prompting skill is anchored on)
into examples/long-horizon-prompt-lab/report/, with SHA-256, source URLs, and
caveats recorded in PROVENANCE.md.
verify_report.py re-extracts the prompt and asserts every block-quote in the
skill's annotated CDC reference appears verbatim in the published source (0 drift
at retrieval), so the skill cannot silently diverge from the primary artifact.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Pseudo-formal task briefs for long-running autonomous agents and parallel
orchestrations: definitions with degenerate cases, exact success predicates,
non-counting outcomes, approach-registry diversity policy, adversarial audit
gates, effort floors, and contamination guards. Anchored on the published
GPT-5.6 Sol Ultra Cycle Double Cover prompt, cross-checked against OpenAI and
Anthropic doctrine and 2025-2026 research.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
- 3 mechanisms: two-split-no-regression-acceptance,
filesystem-experience-archive, runtime-enforced-loop-constraints
(promoted via research_loop.py from run 20260708-034419 after
novelty pass at 0.1246 vs 0.18 threshold and run readiness)
- 6 primary-source claims with provenance
- 2 activation cases for the harness-engineering boundary (21/21 pass)
- Router prompts p051-p053; p036 gains self-improvement-loops as
acceptable secondary
- Corpus index entry mapping scenarios, mechanisms, claims
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Sixteenth skill covering systems where the harness itself is the
optimization target: failure-driven bounded self-edits, meta-harness
search, evolutionary scaffold search, context mechanism evolution, and
acceptance gates for self-modifying systems. Anchored on Weng's
'Harness Engineering for Self-Improvement' (Lil'Log, 2026-07-04) with
all load-bearing mechanisms cross-verified against primary sources
(Self-Harness, Meta-Harness, MCE, ACE, DGM, AlphaEvolve, ShinkaEvolve,
STOP, ADAS, AFlow, METR, Anthropic). Volatile numbers live in a dated
reference file per the claim-provenance policy.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Normalize every SKILL.md description to double-quoted YAML so the corpus,
templates, and examples have one visible convention. Harden frontmatter
parsing against partial fence matches and non-string name/description values,
and extend tests to cover those regressions.
Fix stale or misleading developer-facing docs: remove phantom book-sft plugin
install instructions, document directory-copy installs, add .agents/skills
manual install guidance, fix the digital-brain setup script target, and mark
historical 13-skill analysis as historical. Cut the prepared release metadata
to 2.3.1 across manifests and root SKILL.md.
Tighten production gates by sharing dev dependencies, making orchestrators use
strict repo validation, aligning skill-health required sections with repo
validation, and linting documented plugin install commands against the actual
marketplace manifest.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
* fix: YAML-safe skill frontmatter for cross-platform discovery
Eleven skills used unquoted descriptions containing colons, which strict
YAML parsers reject during skill discovery on Cursor, Claude Code, and
Codex. Normalize all skill frontmatter to valid YAML, add a shared
skill_frontmatter parser with PyYAML validation, fix install docs to use
directory layout, and add .agents/skills symlink plus Open Plugins
skills path declaration.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
* test: add frontmatter parser unit tests and harden examples
Add researcher/scripts/tests/test_skill_frontmatter.py (19 tests) covering
parser edge cases, a strict-YAML regression guard for the unquoted-colon
bug, format/parse round-trips, and corpus + example integration checks.
Wire unit tests into CI ahead of the strict repo gate. Quote the
description fields in the two example skills that had the same
unquoted-colon YAML hazard. Simplify CRLF handling in split_frontmatter
and document CONTRIBUTING test commands.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
* chore: harden production plugin packaging validation
Remove the committed .agents/skills symlink because symlinks are fragile
on Windows checkouts and in plugin packaging. Keep Cursor and Codex
support through Open Plugins discovery and documented directory-copy
manual installs.
Extend validate_repo.py so strict validation checks that the Open
Plugins manifest and Claude marketplace manifest name the same bundled
plugin, and that Open Plugins skills discovery resolves to the same 15
published skills as the repository.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
* ci: certify cross-platform skill compatibility
Add validate_platform_compat.py to check the production surfaces defined by
Agent Skills, Cursor, Claude Code, Codex, and Open Plugins documentation.
The gate validates published skills, manifest discovery parity, and
platform-local directory-copy installs for .cursor/skills, .claude/skills,
.codex/skills, and .agents/skills.
Install skills-ref in CI and require the upstream agentskills reference
validator in the compatibility gate. Tighten manifest path checks so both
Claude marketplace and Open Plugins skill paths must start with './', and
update operator docs to run the new gate before claiming production
readiness.
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>
Embed the four release diagrams (researcher OS pipeline, router leaderboard, skill routing gains, corpus hardening metrics) so the v2.3.0 release notes can link to stable raw GitHub URLs instead of the regenerating draft asset slug.
Co-authored-by: Cursor <cursoragent@cursor.com>
Apply the auto-research quality standard across every published skill and update the mechanisms, claims, fixtures, benchmarks, and release docs so the corpus improves as a coherent system rather than isolated prose edits.
Co-authored-by: Cursor <cursoragent@cursor.com>
muratcankoylan