add_platform.research

Generate CLI configuration and hooks system documentation for platform onboarding.

49|3|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/Unsupervisedcom/deepwork --skill add-platform-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add_platform.research
Source: https://github.com/Unsupervisedcom/deepwork/tree/main/.claude/skills/add_platform.research
Command: npx skills add https://github.com/Unsupervisedcom/deepwork --skill add-platform-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the collection and documentation of a target platform's CLI configuration and hooks system for DeepWork platform integration.

Core Features & Use Cases

  • Capture CLI configuration details, environment variables, and command file formats to inform adapter development.
  • Document slash command hooks and loading mechanisms to guide implementation and testing.
  • Use Case: Onboard a new platform (e.g., Cursor or Windsurf) by generating consistent docs and templates for integration.

Quick Start

Use this skill to generate the platform integration research for a new platform. It will create the documentation files under doc/platforms/<platform_name>/ including cli_configuration.md and hooks_system.md.

Frequently Asked Questions about add_platform.research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document CLI configuration for new platform integration?

Documenting CLI configuration for platform integration involves capturing environment variables, command file formats, and loading mechanisms. This generates structured guidance files under doc/platforms/<platform_name>/cli_configuration.md with source references and example configurations.

What is a hooks system for slash commands?

A hooks system for slash commands defines the loading mechanisms and execution triggers for custom commands within a platform. Documenting this system captures how slash commands are discovered, loaded, and integrated to guide adapter implementation and testing.

How do I onboard a new platform like Cursor or Windsurf for DeepWork integration?

To onboard a new platform like Cursor or Windsurf for DeepWork integration, you generate consistent documentation and templates. This produces structured files detailing the platform's CLI configuration and slash-command hooks under the doc/platforms/<platform_name>/ directory.

Does this platform integration research output include example configurations?

Yes, the platform integration research output includes example configurations. The generated documentation files under doc/platforms/<platform_name>/ contain source references and example configurations for both CLI configuration and the hooks system.

When do I need to generate platform integration documentation?

You need to generate platform integration documentation when onboarding a new platform to inform adapter development. It is required to capture CLI configuration details and document slash command hooks to guide the implementation and testing of the platform integration.