Skip to content

Define the skill entity for generation and curation - #5

Merged
Neverdecel merged 1 commit into
mainfrom
skill-entity
Sep 11, 2026
Merged

Define the skill entity for generation and curation#5
Neverdecel merged 1 commit into
mainfrom
skill-entity

Conversation

@Neverdecel

Copy link
Copy Markdown
Owner

Summary

  • Define a skill as one on-demand job whose description is the discovery index and whose body is the confirmed procedure the agent would get wrong without it.
  • Project that entity into always-on guidance, mining, and curation; stay silent on AGENTS.md, agents, and commands.
  • Tighten generated descriptions (what+when, never Use ONLY when) and tests/scenarios against that shape.

Test plan

  • npm run check
  • npm test
  • Live eval remains opt-in (EVAL_CASE=4 for save-quality).

Treat a skill as one on-demand job with a what+when description, and stay silent on always-on rules, agents, and commands.
@Neverdecel
Neverdecel merged commit 75b99ca into main Sep 11, 2026
1 check passed
@Neverdecel
Neverdecel deleted the skill-entity branch September 11, 2026 05:58
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.

2 participants