freshworks-app-dev-skill

Develop, validate, and migrate Freshworks Platform 3.0 marketplace applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire lifecycle of Freshworks Platform 3.0 application development, from initial creation and debugging to ensuring compliance with the latest platform standards and facilitating migration from older versions.

Core Features & Use Cases

  • Platform 3.0 Enforcement: Guarantees adherence to Platform 3.0 patterns, rejecting legacy 2.x syntax.
  • App Generation: Creates frontend, serverless, hybrid, and OAuth app templates.
  • Automated Validation & Fixing: Runs fdk validate and auto-fixes common errors.
  • Migration Assistance: Helps migrate Platform 2.x apps to 3.0.
  • Use Case: Generate a Freshdesk ticket sidebar app that fetches GitHub issues using OAuth, ensuring all Platform 3.0 best practices are followed, including Crayons UI components and $request.invokeTemplate().

Quick Start

Generate a Freshdesk ticket sidebar app that fetches GitHub issues using OAuth.

Frequently Asked Questions about freshworks-app-dev-skill

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

FAQPage Schema
How do I migrate a Freshworks app from Platform 2.x to 3.0?

To migrate a Freshworks app from Platform 2.x to 3.0, you need to update legacy syntax to enforce Platform 3.0 compliance patterns, rejecting outdated 2.x code structures. This Skill guides you through adapting your codebase to the new platform standards automatically.

What is the best way to build a Freshdesk ticket sidebar app with OAuth?

The best way to build a Freshdesk ticket sidebar app with OAuth is to generate a Platform 3.0 template using this Skill. It scaffolds the app structure while ensuring best practices like implementing Crayons UI components and $request.invokeTemplate() for API integrations.

How does automated validation and fixing work for Freshworks marketplace apps?

Automated validation for Freshworks apps works by running fdk validate to detect Platform 3.0 compliance issues and automatically fixing common errors. This ensures your marketplace application meets submission standards without requiring extensive manual debugging.

Can I use Crayons UI components when generating serverless Freshworks apps?

Yes, you can use Crayons UI components when generating Freshworks apps. This Skill supports app generation for frontend, serverless, and hybrid types, ensuring Crayons UI implementation and Platform 3.0 best practices are followed across different app architectures.

Why does my Freshworks Platform 3.0 app generation fail with legacy syntax?

Freshworks Platform 3.0 app generation fails with legacy syntax because this Skill strictly enforces Platform 3.0 compliance and rejects legacy 2.x patterns. You must update your codebase to use current Platform 3.0 standards to successfully generate and validate your app.