Useful knowledge. Ready for the next task.
Instructions, scripts, and references that help Foxl do specialized work.
Read them. Understand them. Choose what your agent uses.
Get started · Explore the library · Create a skill · Contribute · Licenses
A skill gives an agent a repeatable way to approach a particular kind of work: preparing a document, researching a question, working with a repository, or using a connected service.
Each skill lives in an ordinary folder, starting with a readable SKILL.md. Supporting scripts and reference material stay beside the instructions. This repository is the skill library; Foxl Desktop provides the agent and its runtime.
In Foxl Desktop:
- Open Skills and choose Sync to check this library for updates.
- Review the proposed changes before applying the sync.
- Choose a skill and check its instructions, requirements, and enabled state.
- Try it in chat with a small, concrete task.
“Use the research assistant to turn these sources into a short briefing, with references.”
Some skills ship disabled and need to be enabled before use. Others need a local command, an account connection, or an API key. Each skill's frontmatter and instructions describe those requirements.
To inspect or contribute to the library without changing your installed skills:
git clone https://github.com/foxl-ai/skills.git
cd skillsThe skill folders are under skills/ inside this checkout. Use the app's Skills controls to manage your installed library; cloning this repository alone does not connect external services or install their tools.
Make knowledge readable. Instructions are plain Markdown. You can inspect a workflow before giving it a place in your agent's context.
Be specific about the task. A useful skill says when it applies, what inputs it needs, how to proceed, and how to judge the result.
Put detail where it is needed. Keep the main instructions focused. Longer references, reusable templates, and deterministic scripts belong in supporting files.
Keep choice with the user. Enabled state, tool requirements, and account connections are part of using a skill. Instructions should make those dependencies clear and respect the permissions of the host application.
| Work | Skills |
|---|---|
| Documents | Word · PDF · PowerPoint · Excel |
| Research and knowledge | Research assistant · Notion · Obsidian · Weather |
| Email and workspace | Google Workspace · Outlook · Outlook web fallback · Himalaya · Quip |
| Development | GitHub · Git · Code search · Shell execution · Web fetch · Browser · Electron |
| Coding agents | Coding agent · Claude Code · Codex CLI · Gemini · Gemini CLI · Skill creator |
| Media and audio | Spotify · Spotify player · Sonos · Video frames · YouTube transcript · Local text-to-speech |
| Automation and experiments | Voice calls · tmux · Autoresearch · Healthcheck |
The library includes both everyday workflows and specialized experiments. A folder's presence does not mean its dependencies are installed or that it is enabled by default.
skills/
my-skill/
SKILL.md Instructions and metadata
scripts/ Optional executable helpers
references/ Optional detailed guidance
templates/ Optional starting files
A minimal SKILL.md:
---
name: meeting-brief
description: Turn meeting notes into a brief with decisions, owners, and next steps.
enabled: true
tags: [meetings, writing]
---
# Meeting brief
Use this skill when the user asks to summarize meeting notes.
1. Read the supplied notes and identify the meeting's purpose.
2. Separate decisions from open questions.
3. List next steps with owners and dates only when the notes provide them.
4. Return a concise brief and flag missing information.| Field | Purpose |
|---|---|
name |
Identifies the skill. Use a stable, descriptive name for new skills. |
description |
Explains what the skill does and when it should apply. |
enabled |
Controls whether it is enabled; false allows a skill to ship inactive. |
tags |
Describes its subject or category. |
requires |
Declares required commands, environment variables, or integrations. Existing skills show the supported forms. |
Some built-in skills also declare Foxl runtime tools. Those declarations depend on the host application's implementation; they do not make the checkout a standalone tool server.
In Foxl's Skills page, choose New, then Custom SKILL.md to add your own instructions.
For a contribution to this library:
- Add a folder under
skills/with a clear name and aSKILL.md. - State the task, inputs, prerequisites, and expected result.
- Add scripts or references only when they make the workflow more reliable.
- Try a representative task and check the actual result.
- Include appropriate license and attribution information for material you add.
The skill creator includes guidance and tools for evaluating and improving a skill.
Useful contributions include clearer instructions, corrected commands, better examples, and new workflows with a well-defined purpose.
Open a pull request explaining the task the skill helps with, what changed, and how you exercised it. Include required tools and setup steps. Keep credentials, personal documents, and private service data out of examples.
Report a problem or propose a skill · Foxl documentation
For a security issue, contact security@foxl.ai privately.
The repository's default license is MIT No Attribution (MIT-0). Individual skill licenses also apply.
| Material | License information |
|---|---|
| Repository material without a separate license | MIT-0 |
| Skill creator | Apache-2.0, modified for Foxl (2026-10: instructions rewritten for Foxl, validator made stdlib-only) |
| Other bundled components | Third-party notices |
Read the applicable skill's license before reusing or redistributing its contents.
Part of Foxl · Your day. A little lighter.