SKILL.md instruction file, optional Python tool scripts, and metadata — all discovered and loaded automatically by SkillLoader.
What a skill contains
Every skill is a directory with the following layout:SKILL.md is required. The scripts/ directory is optional but necessary if the skill needs to register executable tools.
The three layers of a skill
Instructions
Markdown content in
SKILL.md that is injected into the agent’s system prompt inside <skills> tags, guiding model behavior for this domain.Tools
Python functions in
scripts/*.py with docstrings and type hints. SkillLoader imports them dynamically and registers their schemas and callables with the agent.Metadata
YAML frontmatter in
SKILL.md parsed into a SkillMetadata object: name, description, version, author, tags, and requires.Built-in skills
Logicore ships two default skills inlogicore/skills/defaults/. They are available by name in any agent without any additional setup.
web_research
Structured web research with multi-source verification. Guides the agent through query analysis, search, source cross-referencing, and synthesis with citations.Tags:
research, web, search, analysiscode_review
Automated code review covering bugs, security vulnerabilities, performance issues, and code quality. Outputs structured findings rated by severity.Tags:
code, review, security, qualitySkills vs. tools
| Tools | Skills | |
|---|---|---|
| Unit | Single callable function | Bundle of instructions + multiple tools |
| Prompt impact | None | Injects domain instructions into system prompt |
| Discovery | Registered manually | Auto-discovered from filesystem |
| Reuse | Per-agent wiring | Load by name across any agent |
| Metadata | None | name, version, author, tags, requires |
scripts/ directory is registered as a tool on the agent, alongside the skill’s instructions.
Architecture
Loading flow
When an agent loads a skill, the following sequence runs:Quick start
Why skills matter
- Consistency — the same instructions and tool bundle are reused across projects and team members, eliminating prompt drift.
- Faster setup — load a named skill instead of wiring tools and prompts individually every time.
- Better quality — domain-specific guidance in
SKILL.mdhelps the model follow the correct workflow for a given task. - Governance —
SkillMetadatafields (name,version,author,tags,requires) make capabilities auditable and versioned. - Composability — multiple focused skills can be combined on a single agent for well-rounded capability.
Next steps
Use skills in agents
Load built-in and custom skills at agent creation or dynamically at runtime.
Build custom skills
Create your own SKILL.md package with custom tool functions and register it in your workspace.