Skip to content

AK-507: reduce actual-skill-openclaw to a redirect stub - #3

Draft
benw5483 wants to merge 1 commit into
mainfrom
ak-507-redirect-stub
Draft

AK-507: reduce actual-skill-openclaw to a redirect stub#3
benw5483 wants to merge 1 commit into
mainfrom
ak-507-redirect-stub

Conversation

@benw5483

Copy link
Copy Markdown

Summary

  • README.md becomes a short redirect notice: this repository is superseded and unmaintained, the canonical actual skill lives at actual-software/actual-skill, the ADR Pre-Check section unique to this variant has been folded in there, and install now points at the canonical README for every surface (Claude Code marketplace, Codex, manual/symlink, clawhub install actual).
  • SKILL.md gets a deprecation admonition at the top of the body, below the frontmatter and above the first heading. The YAML frontmatter is byte-identical to main, so anything still parsing this file for name and description keeps working.
  • No files deleted. LICENSE untouched. No .gitignore added here — that lands in the separate open pull request against this repo.

Sequencing

This depends on the canonical repo's consolidation PR (actual-software/actual-skill#2, open and mergeable), which lands the ADR Pre-Check fold-in, the metadata.openclaw frontmatter, and the ClawHub install section this README points readers toward. That PR also adds the matching "the openclaw variant is superseded by this one" note on the canonical side, so the two READMEs agree in both directions.

Two things are deliberately out of scope and stay with the operator:

  • Archiving this repository. That is a GitHub repo setting, and it is sequenced with the registry cutover rather than with this PR.
  • Any clawhub command. The ClawHub registry serves its own stored copy of the skill and does not read this repository, so clawhub install actual keeps serving the same bytes until someone runs clawhub skill publish with owner credentials. Merging this changes nothing about what the registry serves.

Test plan

This repository has no CI, so verification was manual. What was checked, and how:

  • Frontmatter still parses, name and description present. yaml.safe_load over the delimited block: parses clean, keys ['argument-hint', 'description', 'metadata', 'name'], name non-empty (6 chars), description non-empty (672 chars), metadata.openclaw intact.
  • Frontmatter is unchanged, not merely still-valid. Diffed the delimited block against origin/main byte-for-byte: identical. git diff -- SKILL.md is +3/-0, entirely the banner.
  • Banner sits below the frontmatter and above the first heading. Asserted programmatically against the parsed body; first heading is still # actual CLI Companion.
  • Every README link resolves. All five URLs return HTTP 200: the three cli.actual.ai docs links, the canonical repo, and the canonical #install anchor.
  • No files deleted. git diff --name-status shows M README.md and M SKILL.md only, with no untracked files left behind.

Generated by the operator's software factory.
• City: factory-main · Agent: local-core.builder-1
• On behalf of: @benw5483

actual-software/actual-skill is now the single canonical source for the
`actual` skill. Its open consolidation PR folds in the ADR Pre-Check section
that was this variant's only unique content, along with the namespaced
metadata.openclaw frontmatter block. Nothing here is worth maintaining
separately anymore.

README.md becomes a short redirect notice: superseded, canonical repo named,
ADR Pre-Check confirmed folded in, and install pointed at the canonical
README rather than restated per surface. Restating the Claude Code /
Codex / manual / ClawHub commands here would recreate exactly the drift this
consolidation exists to kill.

SKILL.md gets a deprecation admonition at the top of the body. The YAML
frontmatter is byte-identical to main, verified by diffing the delimited
block, so anything still parsing this file for `name` and `description`
keeps working.

No files deleted, LICENSE untouched, no .gitignore added here — that lands
separately in the open AK-508 pull request against this same repo. Archiving
the repository is a GitHub setting and stays with the operator's registry
cutover, since the ClawHub registry serves its own stored copy and does not
read this repository at all.

Generated by the operator's software factory.
City: factory-main · Agent: local-core.builder-1
On behalf of: @benw5483
Co-Authored-By: <operator-factory-bot> <factory-bot@actual.ai.invalid>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant