Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bastndev/f1/llms.txt

Use this file to discover all available pages before exploring further.

The Local tab is your workspace’s skill inventory. It shows every skill file and skill folder that F1 has detected in the current workspace, along with a global library of skills you have saved for reuse across projects. All changes — whether made from this panel or by editing files directly — are reflected in real time thanks to F1’s file system watchers. Press Alt+3 while the My Skills panel is focused, or run the command f1.mySkills.goLocal from the Command Palette.

​
Two categories of skills

​
Workspace root skills

These are skill files detected at the root of the currently open workspace folder. F1 recognizes the following file names as root skill files:
  • AGENTS.md
  • CLAUDE.md
  • GEMINI.md
  • DESIGN.md
In addition, skill folders installed from the marketplace are tracked under:
  • .agents/skills/<name>/ — for Codex-compatible agents
  • .claude/skills/<name>/ — for Claude Code
Each installed skill folder must contain a SKILL.md manifest file for F1 to display it. The manifest’s name and description fields are shown in the panel.

​
Saved skills

Saved skills are a global library stored in VS Code’s extension global storage. When you save a workspace skill, F1 copies it to the library so it can be reused in other projects. Saved skills are displayed separately and can be enabled in any workspace with a single action.

​
Available operations

Toggle a skill on or off with LocalSkillSetEnabledMessage. Disabling a skill adds it to the .gitignore managed block so it is excluded from agent reads without deleting the file. Enabling it removes the exclusion. F1 manages a dedicated block inside .gitignore (delimited by # My Skills: begin and # My Skills: end) and never touches entries outside that block.
Click the open action for any workspace skill to open its SKILL.md (for folder skills) directly in the VS Code editor. This uses the standard vscode.open command so the file opens in your active editor group.
Saving a skill (LocalSkillSaveMessage) copies the entire skill folder to F1’s global saved-skills library. The skill’s name and description (read from its SKILL.md manifest) are stored in an index file so they can be displayed without reading each folder. A confirmation toast confirms a successful save.
From the saved skills section, click Enable (LocalSkillEnableSavedMessage) to copy a saved skill into the current workspace. F1 presents a quick-pick menu to choose the destination:
ChoiceTarget folder
Recommended.agents/skills/
Claude Code.claude/skills/
If a skill with the same name already exists in the chosen folder, the operation fails with an error so you never silently overwrite an existing skill.
Deleting a workspace skill (LocalSkillDeleteMessage) moves the file or folder to the system trash when possible. F1 asks for confirmation in a modal dialog before proceeding. After deletion, the skills-lock file (skills-lock.json) is updated and empty container folders (.agents/skills/, .claude/skills/) are pruned automatically.
Deleting a saved skill (LocalSkillDeleteSavedMessage) permanently removes it from the global library. F1 confirms this action in a modal dialog with the warning that the removal is permanent and not reversible via the trash.

​
File watching

F1 registers file system watchers for the following patterns so that the Local tab stays in sync without requiring a manual refresh: 
.gitignore
AGENTS.md
CLAUDE.md
GEMINI.md
DESIGN.md
.agents
.agents/skills
.agents/skills/*
.agents/skills/*/SKILL.md
.claude
.claude/skills
.claude/skills/*
.claude/skills/*/SKILL.md
Any create, change, or delete event on these files causes F1 to re-read the workspace and push an updated skill list to the panel. The Create tab’s file-exists indicators also update at the same time.
Skills shown in the Local tab can be attached as context chips in the F1 Prompt Composer. Open the Prompt tool in the CLI Hub, type @, and select a local skill to include its content as structured context in your next agent prompt.

Build docs developers (and LLMs) love

Get started for freeTalk to us