Agent skill

Nocturne Remote Functions

A skill your agent uses when adding API endpoints, creating frontend data fetching, writing +page.server.ts, or connecting Svelte components to backend data in the Nocturne project.

No licenceAuto-check passedBackend & APIs

Install Nocturne Remote Functions

skills CLI

$ npx skills add nightscout/nocturne --skill nocturne-remote-functions -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nightscout/nocturne nocturne-remote-functions --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nightscout/nocturne.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/remote-functions .claude/skills/nocturne-remote-functions && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "nocturne-remote-functions" agent skill from https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions into .claude/skills/nocturne-remote-functions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nocturne-remote-functions", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nightscout/nocturne --skill nocturne-remote-functions -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nightscout/nocturne nocturne-remote-functions --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nightscout/nocturne.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/remote-functions .agents/skills/nocturne-remote-functions && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nocturne-remote-functions" agent skill from https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions into .agents/skills/nocturne-remote-functions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nocturne-remote-functions", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nightscout/nocturne --skill nocturne-remote-functions -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nightscout/nocturne nocturne-remote-functions --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nightscout/nocturne.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/remote-functions .cursor/skills/nocturne-remote-functions && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nocturne-remote-functions" agent skill from https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions into .cursor/skills/nocturne-remote-functions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nocturne-remote-functions", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nightscout/nocturne.git --path .claude/skills/remote-functions

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nightscout/nocturne --skill nocturne-remote-functions -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nightscout/nocturne nocturne-remote-functions --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nightscout/nocturne.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/remote-functions .gemini/skills/nocturne-remote-functions && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "nocturne-remote-functions" agent skill from https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions into .gemini/skills/nocturne-remote-functions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nocturne-remote-functions", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nightscout/nocturne nocturne-remote-functions

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nightscout/nocturne --skill nocturne-remote-functions -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nightscout/nocturne.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/remote-functions .github/skills/nocturne-remote-functions && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "nocturne-remote-functions" agent skill from https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions into .github/skills/nocturne-remote-functions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nocturne-remote-functions", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nightscout/nocturne --skill nocturne-remote-functions -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nightscout/nocturne nocturne-remote-functions --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nightscout/nocturne.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/remote-functions .opencode/skills/nocturne-remote-functions && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nocturne-remote-functions" agent skill from https://github.com/nightscout/nocturne/tree/main/.claude/skills/remote-functions into .opencode/skills/nocturne-remote-functions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nocturne-remote-functions", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: nocturne-remote-functions
GitHub stars: 139
Token cost: ~2.3k tokens
SKILL.md length: 526 words
Files: 1
Skills in repo: 4
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: None found

At a glance

A skill your agent uses when adding API endpoints, creating frontend data fetching, writing +page.server.ts, or connecting Svelte components to backend data in the Nocturne project.

Works in 3 steps: Add the Attribute (Backend) → Rebuild to Generate → Use the Remote Function (Frontend)
Adding API endpoints
SKILL.md covers Overview, The Pipeline, Step 1: Add the Attribute… and Step 2: Rebuild to Generate, plus 5 more sections
Calls dotnet and pnpm

What it does

Nocturne Remote Functions is an agent skill from nightscout/nocturne. Use when adding API endpoints, creating frontend data fetching, writing +page.server.ts, or connecting Svelte components to backend data in the Nocturne project. Triggers on remote functions, server load, apiClient, query/command/form patterns.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering REST APIs. It works with Svelte. The repository describes itself as: A next-generation platform for diabetes management.

When your agent uses it

Adding API endpoints
Creating frontend data fetching
Writing +page.server.ts
Connecting Svelte components to backend data in the Nocturne project

Example prompts

“/nocturne-remote-functions”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Add the Attribute (Backend)
Rebuild to Generate
Use the Remote Function (Frontend)

What it can do on your machine

Read from SKILL.md and the folder at commit 5fabbc5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- dotnet
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nocturne Remote Functions loads about 2.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 526 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~68
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 526 words (~2,264 tokens).

“Nocturne uses a three-stage code generation pipeline that turns C# controller attributes into type-safe SvelteKit remote functions. The generated remote functions are the primary way the frontend fetches data and executes mutations. Never use raw fetch, hand-roll API calls, or…”

— opening of SKILL.md by nightscout

name: nocturne-remote-functions

Outline of SKILL.md

Nocturne Remote Function Toolchain
Overview
The Pipeline
Step 1: Add the Attribute (Backend)
Cache Invalidation
Step 2: Rebuild to Generate
Step 3: Use the Remote Function (Frontend)
Importing
Query (read data)
Command (mutate data)
Accessing .current and .refresh()
When to Write a Hand-Maintained Remote File
What NOT to Do
Never write +page.server.ts for data fetching
Never use raw fetch
Never hand-write what the codegen produces
Never duplicate generated functions in hand-maintained files
Quick Decision Flowchart
Common Mistakes

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/remote-functions of nightscout/nocturne.

Open the folder on GitHubat commit 5fabbc5

Compare with similar skills

Nocturne Remote Functions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nocturne Remote Functions compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nocturne Remote Functions this skillnightscout/nocturne	139	—	~2.3k	Automated safety check: Pass	None	today
Mintlify APImacro-inc/macro	4.6k	2 repos	~333	Automated safety check: Pass	MIT	today
Frappe Ops Website DeployImpertio-Studio/Frappe_Claude_Skill_Package	189	—	~2.5k	Automated safety check: Pass	MIT	22 days ago
Effect Developmentdanieljvdm/effect-cf	111	1 repos	~369	Automated safety check: Pass	MIT	today
Native Triggerwindmill-labs/windmill	18k	—	~7.9k	Automated safety check: Pass	Custom licence	today
Figma Local Dev Loopjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.4k	Automated safety check: Notes	MIT	today

Similar skills

Mintlify API
macro-inc/macro
Interact with the Mintlify REST API to manage deployments, trigger builds, and query documentation site metadata programmatically.
4.6k GitHub starsUsed in 2 repos~333 tokens
Backend & APIsAuto-check passed
Frappe Ops Website Deploy
Impertio-Studio/Frappe_Claude_Skill_Package
Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API.
189 GitHub stars~2.5k tokensUpdated 22 days ago
Backend & APIsAuto-check passed
Effect Development
danieljvdm/effect-cf
Set up Effect, implement Atom React state, HTTP APIs or CLIs, and review Effect architecture.
111 GitHub starsUsed in 1 repo~369 tokens
Backend & APIsAuto-check passed
Native Trigger
windmill-labs/windmill
Guidance for adding native trigger services to Windmill. An agent skill from windmill-labs/windmill.
18k GitHub stars~7.9k tokensUpdated today
Backend & APIsAuto-check passed
Figma Local Dev Loop
jeremylongshore/tons-of-skills-marketplace
Set up a local development workflow for Figma plugin and REST API projects.
2.8k GitHub stars~1.4k tokensUpdated today
Backend & APIsAuto-check: notes
Figma SDK Patterns
jeremylongshore/tons-of-skills-marketplace
Production-ready patterns for the Figma REST API and Plugin API.
2.8k GitHub stars~2.2k tokensUpdated today
Backend & APIsAuto-check passed

Questions about Nocturne Remote Functions

What does Nocturne Remote Functions do?

A skill your agent uses when adding API endpoints, creating frontend data fetching, writing +page.server.ts, or connecting Svelte components to backend data in the Nocturne project. Nocturne Remote Functions is an agent skill from nightscout/nocturne.ts, or connecting Svelte components to backend data in the Nocturne project.

When should I use Nocturne Remote Functions?

Nocturne Remote Functions fits situations like: adding API endpoints; creating frontend data fetching; writing +page.server.ts; connecting Svelte components to backend data in the Nocturne project.

How do I install Nocturne Remote Functions in Claude Code?

Run `npx skills add nightscout/nocturne --skill nocturne-remote-functions -a claude-code`. Or copy the skill folder (.claude/skills/remote-functions in nightscout/nocturne) into .claude/skills/nocturne-remote-functions in your project. Claude Code loads it when a task matches its description.

How do I install Nocturne Remote Functions in Codex?

Run `npx skills add nightscout/nocturne --skill nocturne-remote-functions -a codex`. Or copy the skill folder (.claude/skills/remote-functions in nightscout/nocturne) into .agents/skills/nocturne-remote-functions in your project. Codex loads it when a task matches its description.

Can I use Nocturne Remote Functions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nightscout/nocturne --skill nocturne-remote-functions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nocturne-remote-functions, .gemini/skills/nocturne-remote-functions, .github/skills/nocturne-remote-functions and .opencode/skills/nocturne-remote-functions in your project.

What does Nocturne Remote Functions need to run?

Going by SKILL.md and its folder, Nocturne Remote Functions needs the command-line tools its instructions call (dotnet and pnpm).

Does Nocturne Remote Functions access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nocturne Remote Functions safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nocturne Remote Functions use?

No licence was found for Nocturne Remote Functions or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Nocturne Remote Functions use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nocturne Remote Functions?

Skills that share tags, products or a category with Nocturne Remote Functions: Mintlify API (macro-inc/macro, 4.6k stars), Frappe Ops Website Deploy (Impertio-Studio/Frappe_Claude_Skill_Package, 189 stars), Effect Development (danieljvdm/effect-cf, 111 stars) and Native Trigger (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nocturne Remote Functions?

nightscout (a GitHub organization) maintains it in nightscout/nocturne, which has 139 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.

Source: nightscout/nocturne on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Nocturne Remote Functions

Install Nocturne Remote Functions

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Mintlify API

Frappe Ops Website Deploy

Effect Development

Native Trigger

Figma Local Dev Loop

Figma SDK Patterns

More from nightscout/nocturne

Dev Tenant API

Docs Screenshots

Frontend Testing

Questions about Nocturne Remote Functions

Install Nocturne Remote Functions

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from nightscout/nocturne

Related

Questions about Nocturne Remote Functions