fw-setup

Automate FDK environment setup, version switching, and PATH configuration.

5|2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/freshworks-developers/fw-dev-tools --skill fw-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fw-setup
Source: https://github.com/freshworks-developers/fw-dev-tools/tree/main/skills/fw-setup
Command: npx skills add https://github.com/freshworks-developers/fw-dev-tools --skill fw-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nvm, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The fw-setup Skill automates the installation, configuration, and management of the Freshworks Development Kit (FDK) alongside Node.js versions, streamlining developer onboarding and environment consistency.

Core Features & Use Cases

  • Automated FDK Installation: Installs and manages FDK 10.x on Node 24.11 for Platform 3.0 projects.
  • Version Switching: Facilitates upgrading/downgrading between FDK versions (9.x, 10.x) and Node.js lines (18, 24) with minimal manual effort.
  • Environment Configuration: Ensures PATH and shell configs are correctly set for immediate FDK availability.
  • Troubleshooting Support: Provides diagnostic commands and interactive troubleshooting steps for environment issues.
  • Use in CI/CD and Development: Enables reproducible setups across local and CI environments via scripts and commands.

Quick Start

Run /fw-setup install to setup FDK 10.x with Node 24.11, then verify in a new terminal:

fdk version

Frequently Asked Questions about fw-setup

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

FAQPage Schema
How do I install FDK 10.x and manage Node.js versions for Platform 3.0 projects?

Automated FDK installation manages FDK 10.x on Node 24.11 by configuring Node.js versions via nvm. Running the setup command aligns your shell configurations and PATH, ensuring immediate FDK availability for Platform 3.0 development.

Why does my fdk command stop working after switching Node.js versions?

Switching Node.js versions often causes PATH conflicts that break the fdk command. This setup resolves PATH conflicts and ensures persistent shell configuration across sessions, maintaining seamless FDK version transitions.

Can I use nvm to switch between FDK 9.x and 10.x environments?

Yes, nvm facilitates upgrading and downgrading between FDK versions like 9.x and 10.x. The setup automates version switching with minimal manual effort, aligning the correct Node.js lines like 18 or 24 with your target FDK version.

What is the best way to reproduce my FDK environment setup in a CI/CD pipeline?

Reproducing FDK environments in CI/CD pipelines requires automated scripts that configure Node.js via nvm and Docker. This setup provides scripts and commands that ensure consistent environment alignment and FDK availability across local and CI systems.

Do I need Docker and shell configuration files to automate FDK setup?

Yes, Docker and shell configuration files are required alongside nvm to automate FDK setup. These dependencies allow the system to align environment states automatically, ensuring persistent configuration and resolving PATH issues across sessions.

How do I troubleshoot environment configuration issues when installing the Freshworks Development Kit?

Troubleshooting FDK installation involves running diagnostic commands and interactive steps provided by the setup. It identifies and resolves environment issues like PATH conflicts, ensuring your shell configs are correctly set for FDK availability.