docs(curator): align 'agent-created' definition with actual provenance semantics - #29018
Closed
Twanislas wants to merge 1 commit into
Closed
docs(curator): align 'agent-created' definition with actual provenance semantics#29018Twanislas wants to merge 1 commit into
Twanislas wants to merge 1 commit into
Conversation
…e semantics The curator docs stated that any skill not bundled/hub-installed was 'agent-created' and subject to curation — including foreground-created skills and hand-written ones. Since PR NousResearch#19621 (May 2026), the curator requires an explicit marker in .usage.json, which only the background self-improvement review fork sets. Changes: - Rewrite 'What agent-created means' to document the 3-step eligibility check (not bundled + not hub + created_by=agent marker) - Explain that foreground skill_manage(create) does NOT mark skills as agent-created (user-directed by design) - Warn that hand-written skills are NOT curated - Add note in Per-run reports explaining the '(not resolved)' display when no candidates exist (LLM pass skipped, not a config error) - Link to skill_provenance.py for the write-origin ContextVar Ref: PR NousResearch#19621, tools/skill_provenance.py, tools/skill_manager_tool.py
23 tasks
Contributor
|
This docs update is already present on current Evidence:
|
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
The curator docs stated that any skill not bundled/hub-installed was "agent-created" — including foreground-created skills and hand-written ones. Since PR #19621, the curator requires an explicit
created_by: "agent"marker in.usage.json, which only the background self-improvement review fork sets.Closes #29017.
Changes
1. Rewrite "What agent-created means" section
Before (stale): claimed all non-bundled/non-hub skills were curated — including foreground
skill_manage(create)calls and hand-written skills.After: documents the actual 3-step eligibility check:
created_by: "agent"oragent_created: truein.usage.jsonExplains that only the background review fork sets this marker, and that foreground-created skills are intentionally excluded (user-directed by design). Warns that hand-written skills are NOT curated.
2. Add note on
(not resolved)display in reportsWhen no agent-created candidates exist, the LLM pass is skipped and the report shows
Model: (not resolved) via (not resolved)withDuration: 0s. This is expected behavior, not a config error. Added a:::notecallout in the Per-run reports section.3. Link to provenance internals
References
tools/skill_provenance.py(write-origin ContextVar) andmark_agent_created()so users who want to understand the mechanism can trace the code.Files changed
website/docs/user-guide/features/curator.md: +45 −21 linesVerification
No code changes — docs only. The provenance semantics described match the current behavior in:
tools/skill_provenance.py—BACKGROUND_REVIEWContextVar,is_background_review()tools/skill_manager_tool.py—mark_agent_created()gate at line 782tools/skill_usage.py—_is_curator_managed_record(),list_agent_created_skill_names()