Factory Droid — Skills

File format

Markdown

Discovery path

.factory/skills

Global install path

~/.factory/skills

Syllago install method

Symlink, Direct copy

Symlink support

Yes

Native frontmatter fields

name, description, license, compatibility, metadata

Features

How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.

Fields

Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.

Provider field	Conversion	Canonical key	Summary
description	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	description	yaml frontmatter key: description (recommended, not required)
disable-model-invocation	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	disable_model_invocation	yaml frontmatter key: disable-model-invocation (optional bool, default: false)
name	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	display_name	yaml frontmatter key: name (optional, defaults to directory name)
user-invocable	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	user_invocable	yaml frontmatter key: user-invocable (optional bool, default: true)

Other features

Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.

Feature	Conversion	Summary
Auto-Invocation	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	The Droid automatically invokes matching skills based on the description field; gated by user-invocable and disable-model-invocation flags.
canonical_filename	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	SKILL.md (fixed, required filename within the skill directory)
custom_filename	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	skill.mdx is accepted as an alternative to SKILL.md within the skill directory
global_scope	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	~/.factory/skills/<skill-name>/SKILL.md
project_scope	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	<repo>/.factory/skills/<skill-name>/SKILL.md
Supporting Files	Preserved Conversion type: Preserved Syntax survives conversion but the target provider may not interpret it. Learn more →	Co-located scripts, schemas, or checklists alongside SKILL.md that the Droid can reference, enabling self-contained skill packages.
Legacy Commands Compatibility	Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more →	Files under .factory/commands/ are still loaded for backwards compatibility, though skills are now the preferred mechanism.
Monorepo Skill Paths	Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more →	Skills may live in per-project .factory/skills/ directories or a shared root-level .factory/skills/ for monorepo organization.
Skill Composability	Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more →	The Droid can chain multiple skills within a single plan, composing reusable primitives instead of building monolithic skills.

Sources

Source
https://docs.factory.ai/cli/configuration/skills