sn-sdk-fluent

Generate ServiceNow Fluent SDK .now.ts metadata definitions with correct imports and constraints.

15|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/aatrey882/servicenow-agent-skills --skill sn-sdk-fluent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sn-sdk-fluent
Source: https://github.com/aatrey882/servicenow-agent-skills/tree/main
Command: npx skills add https://github.com/aatrey882/servicenow-agent-skills --skill sn-sdk-fluent

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Prevents AI-generated ServiceNow Fluent SDK code from hallucinating incorrect metadata types, missing required fields, or using wrong import paths, so your generated .now.ts files compile and deploy as spec-compliant artifacts.

Core Features & Use Cases

  • Routing-only entry + reference-driven generation: reads only the needed reference docs before writing Fluent metadata code, keeping answers precise and context windows small.
  • ServiceNow Fluent metadata correctness: enforces documented constructors, required $id rules, and correct usage of Now.ID/Now.include and scope prefix from now.config.json.
  • Safe authoring guardrails: prohibits GlideRecord usage and blocks incorrect imports from @servicenow/sdk (must use @servicenow/sdk/core), reducing framework mismatches.
  • Supports common metadata types: tables, ACLs, business rules, client scripts, script includes, flows, REST APIs, Service Portal widgets/pages/themes/menus, UiAction, and UiPage.

Quick Start

Ask your agent to generate a Fluent Table and include a ReferenceColumn to sys_user using the scope prefix from your now.config.json.

Frequently Asked Questions about sn-sdk-fluent

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

FAQPage Schema
How do I generate correct ServiceNow Fluent SDK metadata for .now.ts files?

To generate correct ServiceNow Fluent SDK metadata for .now.ts files, use a routing-based generation process that reads reference docs first, enforcing proper constructors, $id rules, and Now.ID usage. This prevents hallucinated types and wrong SDK import paths in your Fluent DSL projects.

Why does my AI-generated ServiceNow Fluent code use incorrect import paths?

AI-generated ServiceNow Fluent code often hallucinates incorrect import paths because it lacks framework context. Enforcing imports specifically from @servicenow/sdk/core ensures your generated metadata code compiles and deploys as spec-compliant artifacts without framework mismatches.

Can I use GlideRecord in ServiceNow Fluent SDK metadata definitions?

No, you cannot use GlideRecord in ServiceNow Fluent SDK metadata definitions. Authoring guardrails explicitly prohibit GlideRecord usage to ensure your .now.ts files remain spec-compliant and deployable within the Fluent DSL framework architecture.

What ServiceNow Fluent metadata types are supported for code generation?

Supported ServiceNow Fluent metadata types include tables, columns, ACLs, business rules, client scripts, script includes, flows, REST APIs, Service Portal widgets, pages, themes, menus, UiAction, and UiPage. The generation process enforces required $id rules and correct constructors for each type.

How do I configure the scope prefix for ServiceNow Fluent SDK tables and columns?

To configure the scope prefix for ServiceNow Fluent SDK tables and columns, source the prefix directly from your now.config.json file. This ensures generated metadata definitions match your application's scope and compile correctly as spec-compliant artifacts.

What's the best way to stop AI from hallucinating missing $id requirements in Fluent SDK code?

The best way to stop AI from hallucinating missing $id requirements in Fluent SDK code is to use reference-driven generation that enforces documented constructors and mandatory $id rules before writing metadata. This ensures your .now.ts files deploy without validation errors.