Add Cline integration (Skills support)

[oinayat]

Hi! First-time contributor here. I use Cline as my day-to-day agentic coding tool and have put together Cline support as a new integration. I wanted to share the approach here first and get some feedback before opening a PR.

Approach

Cline Skills use the same SKILL.md structure already supported by the skill-md format, so I’ve reused that rather than introducing a new format. I also followed the existing integration patterns in the repo, particularly Mistral Vibe (#658) for the tools.json structure and Osaurus (#603) for the skill-md converter.

The changes include:

• Added Cline to tools.json with user and project scope, .cline/skills/{slug}/SKILL.md destinations, and the agency- slug prefix.
• Added convert_cline() to convert.sh and wired it into the existing tool handling.
• Added Cline detection and install_cline() to install.sh.
• Added Cline to the agency-skill path collision group, since it writes the same agency-<slug>/SKILL.md filenames as Antigravity and Osaurus. I also verified that the installer rejects a shared --path for Antigravity + Cline.
• Added the generated-output rule to .gitignore.
• Added integrations/cline/README.md.
• Added Cline to scripts/test-convert-outputs.sh.

Global/user scope is the default (~/.cline/skills/), with project-scoped installs available through --path, following the existing installer convention for dual-scope tools.

Validation

• scripts/check-tools.sh passes with all 17 tools consistent.
• scripts/test-convert-outputs.sh --update passes when run from WSL. The manifest currently uses OS-native path separators, so the generated hashes differ when the script is run from Windows.
• I installed the real generated output into ~/.cline/skills/ and confirmed that a skill loads correctly in a live Cline chat session using /agency-frontend-developer.

Cline-specific issues

While testing, I also came across two Cline issues that are unrelated to the installer itself:

• Skills don't appear in the / slash-command suggestion menu in the VS Code extension, although typing the full command and pressing Enter works: [cline#13805](Skills never appear in the slash command menu in the VS Code extension (docs & v4.1.4 changelog say they should) cline/cline#13805).
• Cline's "create new skill" UI writes to ~/.agents/skills/, while its runtime reads from ~/.cline/skills/: [cline#12523](Plugin stores skills in ~/.agents/skills but reads from ~/.cline/skills/ cline/cline#12523).

Both are documented in integrations/cline/README.md under Known Issues so users can distinguish Cline-side behavior from integration problems.

Question

Does this approach look right, particularly reusing skill-md and using global/user scope by default with --path for project installs?

The integration is already implemented and tested locally, so I’d like to make sure the approach fits the project’s conventions before opening the PR.

Thanks for taking a look!