Adding now-sdk skills

[ShantanuPhadke]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the staged branch for this pull request.

---

Description

Agent skills for building ServiceNow applications using ServiceNow Fluent, a TypeScript-based DSL for defining platform metadata in code. These skills teach Copilot how to use the @servicenow/sdk CLI to look up API types, metadata conventions, and project structure before generating or editing code.

Includes two skills: now-sdk-explain, which fetches live SDK documentation via npx @servicenow/sdk explain and triggers automatically when working in a Fluent project; and now-sdk-setup, which validates that Node.js 20+ and @servicenow/sdk v4.6.0+ are configured correctly.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify):

---

Additional Notes

Note: I'm a ServiceNow employee.

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔍 Skill Validator Results

⚠️ Warnings or advisories found

Scope	Checked
Skills	2
Agents	1
Total	3
Severity	Count
---	---:
❌ Errors	0
⚠️ Warnings	2
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	Found 2 skill(s)
ℹ️	[now-sdk-explain] 📊 now-sdk-explain: 702 BPE tokens [chars/4: 720] (detailed ✓), 5 sections, 4 code blocks
ℹ️	[now-sdk-explain] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably.
ℹ️	[now-sdk-setup] 📊 now-sdk-setup: 303 BPE tokens [chars/4: 277] (compact ✓), 2 sections, 1 code blocks
ℹ️	[now-sdk-setup] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably.
ℹ️	✅ All checks passed (2 skill(s))

Full validator output

```text Found 2 skill(s) [now-sdk-explain] 📊 now-sdk-explain: 702 BPE tokens [chars/4: 720] (detailed ✓), 5 sections, 4 code blocks [now-sdk-explain] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [now-sdk-setup] 📊 now-sdk-setup: 303 BPE tokens [chars/4: 277] (compact ✓), 2 sections, 1 code blocks [now-sdk-setup] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. ✅ All checks passed (2 skill(s)) ```

[aaronpowell]

This skill isn't really useful, agents are pretty efficient at checking versions of packages and it also embeds some practices that aren't ideal, such as forcing global install and not checking package.json, so I wouldn't include it.

[aaronpowell]

Is calling it the now-sdk going to be discoverable enough for users, or would /servicenow-sdk-explain be better since then it's clear that it's related to ServiceNow?