Harden skill contracts and portfolio integrity - #22
Merged
Conversation
mosobande
force-pushed
the
feature/lightweight-skill-contracts
branch
from
August 22, 2026 15:37
0beab25 to
181cf7a
Compare
mosobande
force-pushed
the
feature/lightweight-skill-contracts
branch
2 times, most recently
from
August 22, 2026 17:29
4bf4d6e to
ff421f3
Compare
mosobande
force-pushed
the
feature/lightweight-skill-contracts
branch
from
August 22, 2026 18:03
5e9c26e to
688810c
Compare
There was a problem hiding this comment.
🤖 Alátùńwò AI review · 📄 Diff-only
Reviewed from the pull request diff only (no surrounding files).
This PR hardens provider credential isolation, simplifies release ownership, and refines skill contracts. No blocking issues found; runtime behavior could not be independently verified from the supplied diff.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change tightens the Engineering and Productivity skill portfolio while preserving deliberately lightweight skills instead of expanding them into workflow-heavy contracts.
Skill behavior
ko-skillto classify skills aslightweightorworkflowbefore judging instruction depth;iwadilightweight while reporting material primary-source conflicts and limiting evidence gaps;se-triagecomplete its current assessment before asking permission for an unapproved relevant external/provider mutation;technical-writingauthority to edityo-slop;ro-wo,salaye, and Alága without speculative workflow expansion or extraction.Provider safety
seda-prandwo-pr;Release ownership
package-lock.jsonduringnpm run versioninstead of editing it with a custom synchronizer;VERSIONfile and hard-coded README version marker;/releases/latestendpoint;npm ci) and the two provider test suites;ko-skilland review rather than a second permanent registry checker.Design decisions
Broad applicability does not by itself justify workflow state, phases, retries, or recovery machinery. A lightweight skill may still produce one composed artifact when that native result closes its outcome.
Cross-skill dependency metadata remains absent because the current Agent Skills metadata surface provides no dependency semantics.
Verification
Final parent candidate:
688810c1dfa8cb40b9af647a493d667edf7e3522.The release simplification removes custom generated-state machinery rather than replacing it:
npm ciis the package/lock consistency gate, Changesets updates the package version, and npm owns lockfile regeneration. Provider unit tests remain unchanged from the previously accepted candidate.The
se-triagepermission rule preserves its existing authority model and provider-write safeguards. Irinṣẹ and Àyẹ̀wò Ìgbà Iṣẹ́ remain behavior-preserving progressive-disclosure changes. The proposed Alága extraction remains rejected because candidate, proof, documentation, and review gates are too coupled to the core delivery path.Stack
This PR is the non-design parent for design PR #9. PR #9 is based directly on this parent head; design-specific ownership and routing changes remain in the child.
Review focus
se-triageend-of-assessment mutation-permission boundary;ko-skill;Contributor: @mosobande