Skip to content

v0.6.7

Choose a tag to compare

@github-actions github-actions released this 06 Aug 09:42
· 66 commits to main since this release
6183c2c

Added

  • Added support for the open Agent Skills specification. Or now discovers user
    Skills from ~/.agents/skills/<name>/SKILL.md and workspace Skills from
    <workspace>/.agents/skills/<name>/SKILL.md, with workspace Skills taking
    precedence when names collide.
  • Added a curated, redistributable Skill collection under skills/. The first
    packages are Vercel Labs' MIT-licensed find-skills and iOfficeAI's
    Apache-2.0-licensed officecli, with pinned upstream revisions and licenses.
    They can be installed from GitHub with commands such as
    npx skills add ktsoator/or@officecli -g -y.

Changed

  • Unified built-in commands, Prompt Templates, and Skills under the composer's
    / menu. Opening the menu refreshes both file-backed catalogs, and a Skill
    remains distinct from a same-named Prompt Template.
  • Preserved activated Skill instructions as protected session context across
    compaction and session restoration. Repeated activation reuses the original
    instruction snapshot instead of loading a changed file mid-conversation.
  • Omitted the Skill catalog, protocol text, and tool entirely when no valid
    Skills are available.
  • Tightened SKILL.md validation to the standard fields and naming limits.
    Skill bodies are loaded unchanged, relative paths resolve from the Skill
    directory, and allowed-tools never bypasses Or's permission policy.

Upgrade Notes

  • Move existing Skills from ~/.or/skills/ to ~/.agents/skills/, and move
    workspace Skills from <workspace>/.or/skills/ to
    <workspace>/.agents/skills/.
  • The composer no longer uses $ to open Skills. Use / for commands, Prompt
    Templates, and Skills.
  • Legacy prompt-template substitution and nonstandard top-level Skill fields are
    no longer supported. Put version information under metadata.version.
  • Bundled resources in user-level Skills remain outside the workspace and may
    require normal read approval. Executing a bundled script continues to use the
    normal command permission flow.

Full Changelog

Compare v0.6.6...v0.6.7