> For the complete documentation index, see [llms.txt](https://skyforgeai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://skyforgeai.gitbook.io/docs/use/examples.md). # Example Prompts Real prompts you can use with SkyForge. Copy, adapt, and run them in a new session. *** ## Incidents & Business Rules ``` Query the last 5 critical incidents Create a Business Rule on incident that sets priority to 1 when category is security and impact is 1 Create a Business Rule on incident that fires after insert and update, checks if the assigned_to field is empty, and sends an email notification to the assignment group manager asking them to assign the ticket ``` *** ## Flow Designer ``` Create a Flow Designer flow that triggers when a P1 incident is created, sets state to In Progress, and creates an incident task if category is software Create a Flow Designer flow on the change_request table that triggers when a change moves to the Review state — it should send an approval to the CAB manager, wait for the decision, and if rejected set the change state back to Draft with a work note explaining why Create a subflow called "Send Escalation Notification" that takes an incident sys_id as input, looks up the assignment group manager, and sends them an email with the incident number, priority, and a direct link to the record ``` *** ## Process Automation Designer (Playbooks) SkyForge reads and builds Process Automation Designer (PAD) playbooks — the guided, lane-and-activity workflows used for guided setup, remediation, and approval-driven processes. It works through ServiceNow's own PAD APIs, so playbooks come out fully usable in Workflow Studio, not just structurally similar. ``` List all the playbooks on this instance and tell me which ones are active Read the "Server Patch Remediation" playbook and show me its full lane and activity structure, including start rules and dependencies Create a Process Automation Designer playbook called "New Hire IT Setup" with two lanes: 1. "Account Provisioning" — create the user's AD account, then create their email account (after AD account) 2. "Equipment" — starts after Account Provisioning completes — order a laptop, then schedule an IT orientation call (after laptop is ordered) Look up real activity definitions first — don't guess sys_ids. Add a trigger that fires on record create on the sys_user table where u_employment_status=new_hire. ``` ``` Update the "New Hire IT Setup" playbook — add a third lane called "Verification" that starts after Equipment completes, with one activity "Confirm all access granted" that verifies the AD account, email, and laptop are all provisioned. Add a variant called "Contractor" with condition u_employee_type=contractor for a lighter-weight setup path. ``` > **Discover before you build:** SkyForge always looks up real activity definitions, trigger types, and (for any activity type it hasn't configured before) the live input schema before creating or updating anything — never guessed sys\_ids or field names. If SkyForge seems to skip this on a complex request, ask it to check the schema first. > **Any activity type works:** Not just "Create task" — Iframe, External Links, Checklist Task, Knowledge Article, Questionnaire, Decision, and any custom flow-backed activity definition in your instance are all supported the same way. > **Table names for triggers:** SkyForge validates trigger table names against the instance before creating anything, so a wrong or invented table name (e.g. a guessed name that doesn't exist) fails fast with a clear error instead of silently creating a broken trigger. *** ## Service Catalog ``` Create a catalog item called "New Laptop Request" on the Service Catalog with two variables: "laptop_model" (label: "Laptop Model", single line text, mandatory) and "justification" (label: "Business Justification", multi-line text). Then create a Flow Designer flow that triggers when the catalog request is submitted — it should send an approval to the requester's manager, and if approved, create an incident with short description "Laptop approved for [requester name]" Create a catalog item called "VPN Access Request" with variables for employee name, start date, manager approval, and reason for access. Add a variable set for IT contact details. Create a catalog client script that makes the manager approval field mandatory only when the employee type is Contractor Create a catalog item called "Office Supply Request" with a variable set containing: item name (choice field with options: pen, notebook, stapler, mouse), quantity (integer, mandatory, max 10), and delivery location (reference to cmn_location). Add a UI policy that hides the delivery location field when quantity is greater than 5 ``` *** ## Dashboards & Reporting ``` Create a Platform Analytics dashboard called "Incident Overview" with three widgets: a bar chart showing incidents by category for the last 30 days, a donut chart showing incidents by state, and a KPI widget showing average resolution time in hours Create a dashboard called "Change Management Health" with a trend chart showing change requests by type over the last 90 days, a table widget listing all open emergency changes, and a gauge showing the percentage of changes implemented successfully this month Create a report showing all incidents created in the last 7 days grouped by assignment group, with columns for number, short description, priority, state, and assigned_to. Schedule it to run every Monday at 8am and email it to the IT manager group ``` *** ## Automated Test Framework (ATF) ``` Create an ATF test called "Incident Priority Calculation" that: 1. Creates a test incident with category=security and impact=1 2. Runs the business rule that sets priority 3. Asserts that the priority field equals 1 4. Cleans up the test record after the test completes Create an ATF test suite called "Catalog Request Flow" that tests the New Laptop Request catalog item end-to-end — submit a request, verify the approval task is created for the manager, approve it, and assert that the resulting incident was created with the correct short description Create an ATF test for the "Auto-assign incident by category" business rule — create test incidents with different categories, run the rule, and assert each one is assigned to the correct assignment group based on the lookup table ``` *** ## Service Portal Widgets ``` Create a Service Portal widget called "My Open Incidents" that shows a table of the current user's open incidents with columns for number, short description, priority, and state. Clicking a row should open the incident in a new tab. Add a refresh button that reloads the data without a full page reload Create a Service Portal widget called "Incident Stats" that shows three KPI cards side by side: total open incidents, average resolution time in hours, and number of P1 incidents this month. Each card should have an icon, a large number, and a label. Pull all data from the server script using GlideAggregate Create a Service Portal widget called "Team Workload" that displays a bar chart (using Chart.js) showing the number of open incidents per assignment group. The server script should query the incident table, group by assignment group, and return the counts. The client controller should initialise the chart on load and refresh every 60 seconds ``` *** ## Service Portal — Full Portal from a Design SkyForge can build a complete Classic Service Portal (sp\_page / sp\_widget / Bootstrap 3) from screenshots, images, or a text description. Attach all your design images (one per page or a collage) and use the prompt below. SkyForge will produce a full build plan — theme + every page — for you to approve before creating any records. ``` Build a [PORTAL NAME] Service Portal from the attached design images. This is Classic Service Portal (sp_page / sp_widget / Bootstrap 3) — NOT UI Builder. I have attached [N] design image(s) showing the following pages: - [Page 1 name, e.g. Homepage / Engage SOLV] - [Page 2 name, e.g. Manager Hub] - [Page 3 name, e.g. Requests] - [Page 4 name, e.g. Welcome / Onboarding] (list all pages visible in the designs) Load the service-portal skill. Analyze ALL attached images and produce a build plan covering: 1. THEME — one shared theme for the whole portal. Sample exact hex values from the designs for each design_tokens field: - brand_primary: primary buttons, active states, brand accent color - accent: selected tabs, highlighted states ($select-primary) - background_secondary: page canvas background - background_primary: cards, panels, surfaces (usually white) - text_primary: headings and body text - text_tertiary: muted / secondary text - border_color: card borders, dividers, input borders - link_color: hyperlinks - font_family: body font (e.g. "Inter", sans-serif) - navbar_bg: top navigation bar background - border_radius_base: corner roundness in px (e.g. 4px or 12px) Note any per-page color variations (e.g. dark footer band, hero overlay) that go in widget/container CSS rather than the theme. 2. PAGES — for each page in the design: - Page id (url-safe, e.g. homepage, manager_hub, requests, welcome) - Page title - Is this the portal homepage? (yes/no) - Layout: containers top-to-bottom with columns (Bootstrap 12-grid, size_lg) and which widget fills each slot — mark each OOB or custom. 3. CUSTOM WIDGETS — list only sections no OOB widget covers, across ALL pages. One-line spec per widget. Note which pages reuse the same widget. 4. NAVIGATION — top nav labels, any mega-menu topics visible in the designs. 5. OPEN QUESTIONS — anything ambiguous you need confirmed before building. Output this as the plan. Do not create any records until I approve. On approval, build in this order: 1. Confirm scope and create an update set named "Feature: [PORTAL NAME] Portal". 2. sn_create_portal_theme with design_tokens — confirm NO SCSS compile error and report theme sys_id before continuing. 3. Create ALL sp_pages (one per page in the design). 4. Create sp_portal referencing the theme and the homepage sp_page. 5. Create shared custom sp_widgets once — reuse across pages that share them. Use .sassvars pattern so widgets inherit theme variables, no hardcoded colors. 6. sn_build_portal_layout for EACH page top-to-bottom. 7. Configure OOB widgets, quick links, taxonomy, and navigation menu. 8. Validate each page with sn_discover_portal and check against the designs. ``` > **Tip:** Attach all page designs in the same message. If you have a collage image showing multiple pages side by side, that works too — tell SkyForge which page is which in the prompt. > **Reasoning:** Use low or medium reasoning for build steps — high reasoning can stall the stream on long multi-page runs. The plan-first approach (approve before building) is more reliable than a single one-shot prompt, especially for portals with 3+ pages. > **Custom fonts:** `font_family` sets the SCSS variable only. If the design uses a non-ESC font, also add a CSS `@import url(...)` in `css_variables` or a CSS include — otherwise the browser falls back. > **Shared widgets:** Identify widgets that appear on multiple pages (e.g. a dark footer band, a hero carousel) during the plan step. Build them once and reuse the same sp\_widget sys\_id across pages — do not create duplicates. You can also add pages to an existing portal individually: ``` Add a Manager Hub page to the existing [PORTAL NAME] portal (theme sys_id: XXXX). Page id: manager_hub Page title: Manager Hub From the attached design, build the layout: - Full-width status tiles row: Your Team Today (Onboarding / Offboarding / Movements counts) — custom widget - Full-width journeys attention cards: lg=12 (OOB Journey cards or custom) - Two-column requests section: lg=8 open requests carousel, lg=4 quarterly focus cards (OOB + custom) - Reuse the existing dark footer widget from the homepage Do not create a new theme or portal — attach to the existing one. Report the new page sys_id when done. ``` ``` Create a portal theme called "Acme Theme" with these design tokens: - brand_primary: #1B6BFF (primary buttons, links, active states) - accent: #1B6BFF (selected tabs and highlights) - background_secondary: #F4F5F7 (page canvas) - background_primary: #FFFFFF (cards and surfaces) - text_primary: #111827 - text_tertiary: #6B7280 - border_color: #E5E7EB - link_color: #1B6BFF - font_family: "Inter", sans-serif - navbar_bg: #0A2540 (dark navy header) - border_radius_base: 8px Create these pages under the Acme portal (portal sys_id: XXXX): 1. Homepage (id: acme_home) — search bar, quick links + my items split, helpful applications grid, dark footer 2. Requests page (id: acme_requests) — request list lg=9 + filter panel lg=3 3. Welcome page (id: acme_welcome) — hero welcome banner, progress steps, things to know, helpful applications Create a taxonomy called "Acme Employee" with root topics: Technology Services, HR & People, Finance & Expenses, Facilities. Under Technology Services add: Hardware, Software, Network. ``` *** ## Now Experience Workspace SkyForge builds a complete Now Experience workspace end-to-end — shell, navigation, list panel, PAR dashboard, audience, and workspaces menu registration — in a single session. ### Simple ITSM Workspace with PAR Dashboard Home ``` Build a Now Experience workspace called **Inmorphis** at path `inmorphis` in global scope. Tables: `incident`, `change_request`, `problem`. Access: `itil` role. **PAR Dashboard** named "Inmorphis" with one tab "Overview": Row 1 — 4 single score widgets (w:12, h:14 each): - Open Incidents — `incident`, filter: `active=true` - High Priority — `incident`, filter: `priority=1^active=true` - Open Changes — `change_request`, filter: `active=true` - Open Problems — `problem`, filter: `active=true` Row 2 — 2 bar charts (w:24, h:20 each): - Incidents by Priority — `incident`, filter: `active=true`, group_by: `priority` - Changes by State — `change_request`, filter: `active=true`, group_by: `state` Row 3 — 2 charts (w:24, h:20 each): - Problems by Category — `problem`, filter: `active=true`, group_by: `category`, type: `donut` - Incident Trend — `incident`, trend_field: `sys_created_on`, frequency: `month`, type: `line` **Left nav** (chrome_toolbar): - Home — icon: `home-outline`, route: `home` - Incidents — icon: `list-outline`, route: `list` - Analytics Center — icon: `analytics-center-outline`, route: `analytics-center` **Plus menu** (chrome_tab): New Incident (`incident`), New Change (`change_request`), New Problem (`problem`) **List panel**: incidents (`active=true`), changes (`active=true`), problems (`active=true`) **Audience**: `itil` role wired to workspace and all lists. **Workspaces menu**: add to Workspaces category. After all setup, wire home page to the PAR dashboard using `sn_wire_dashboard_home`. ``` > **Tip:** Replace the name, path, tables, roles, widgets, and nav items to match your use case. The build order is automatic — SkyForge handles the full sequence end-to-end. > **Dashboard home:** The PAR dashboard is wired to the home page via `sn_wire_dashboard_home` — always the last step. Do not add any further instructions about modifying the home page after this. *** ``` Deploy my changes to a new Update Set called "Sprint 24 Changes" Create a new Update Set called "Feature: VPN Access Catalog Item", make it current, then create the catalog item and flow, and complete the Update Set when done ``` *** ## Decision Builder ``` This logic has multiple conditions mapping to outputs — create a Decision Table called "Incident Routing" that routes incidents to the right assignment group based on priority and category. Priority 1 + network → Network Ops, Priority 1 + software → App Support, anything else → Service Desk Create a Decision Table called "Change Risk Approval" with inputs for change type (choice: standard, normal, emergency) and CI count (integer, mandatory). Output an approval group (reference to sys_user_group) — emergency changes always go to CAB, normal changes with more than 50 CIs go to Change Manager, everything else goes to the requesting team's manager Create a Decision Table called "Discount Tier" for a product catalog — inputs are item category (choice) and order total (integer), output is a discount percentage (integer) and whether to escalate for manual approval (boolean) when the discount exceeds 20% List all the decision tables on this instance and show me what each one does Evaluate the "Incident Routing" decision table with priority=1 and category=network and tell me what group it resolves to I have this if/else chain in a business rule — [paste code] — convert it into a Decision Table instead so the business team can maintain the routing rules without needing a developer ``` > **Tip:** Decision Builder is a great fit whenever routing, assignment, or categorization logic has several conditions mapping to outputs and business users (not developers) should be able to update it later. SkyForge will proactively suggest a Decision Table if you're describing multi-condition if/else logic in a business rule, flow, or script. > **Scope:** If you're working inside a scoped application, say so up front (e.g. "in the x\_acme\_app scope") — SkyForge will use that scope for the decision table rather than defaulting to global. > **Build everything in one shot:** Include inputs, answer elements, AND all rows in the same create request — don't split table creation and row population across separate turns. If a table does end up with no rows (or you want to add more later), SkyForge can add rows to an existing table without recreating it. *** ## AI Agents, Agentic Workflows & Now Assist Skills ``` Create an AI agent that assesses risk for new change requests — it should fetch the change details, check for related past changes, and write a risk summary as a work note Create an agentic workflow for HR onboarding — one agent gathers employee details and checks what accounts need to be created, a second agent sends the welcome email and creates the IT access tasks Create a Now Assist skill called "Summarize Incident for Customer" that takes an incident record as input and writes a plain-language summary of the issue and current status for the customer Create a Now Assist skill that fetches incident details, with a script tool that looks up the incident categories from sys_choice Create a Now Assist skill that researches an issue online using a web search tool before writing its response Show me what AI agents, tools, and Now Assist skills already exist on this instance before creating anything new ``` *** ## Finding Tools SkyForge has 393+ tools, lazy-loaded. Search for what you need: ``` search for catalog item tools search for flow designer tools search for CMDB tools search for ATF tools ```