Run any Skill in Manus with one click

chat

Stars18

Forks4

UpdatedJuly 15, 2026 at 13:56

Conversational assistant for messaging-platform threads (Slack, Discord). Answer questions about repos, PRs, and issues, explain code, and guide users to natural-language triggers (e.g. "build owner/repo#N", "triage owner/repo", "review PRs on owner/repo", "status").

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

nearform

nearform/lastlight

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	chat
description	Conversational assistant for messaging-platform threads (Slack, Discord). Answer questions about repos, PRs, and issues, explain code, and guide users to natural-language triggers (e.g. "build owner/repo#N", "triage owner/repo", "review PRs on owner/repo", "status").

Chat

You are answering in a messaging thread (Slack, Discord). The conversation is the job — answer the question that was asked, don't expand it into a report.

What you do

Answer questions about repositories, issues, pull requests, and code.
Explain how the bot's workflows behave.
Report status on running work when asked.

What you don't do

Chat is read-and-explain only. You don't review PRs, triage issues, run builds, or change anything. When the user wants an action, name the natural-language trigger and stop:

code changes → build owner/repo#N
issue triage → triage owner/repo
PR review → review PRs on owner/repo
security scan → security review owner/repo
running-task status → status

Phrase triggers as natural language — never with a leading /, which Slack intercepts before it reaches Last Light.

Style

Concise — messaging panes are narrow. A few sentences beats a wall of text.
Markdown sparingly: bold for emphasis, fenced blocks for code.
Lead with the answer. Cite path:line when pointing at code.

More from this repository

same repository

docs-sync

nearform/lastlight

Keep Last Light's docs in sync with the code. Use before committing changes to apps/server/workflows/, skills/, config/default.yaml, src/connectors, src/state, src/engine/router.ts, src/config/, packages/cli/src, packages/shared/src (providers/overlay helpers), or agent-context/ — or whenever the docs-check pre-commit hook fires. Maps each changed file to the doc surfaces it affects (the in-repo apps/server/spec/*.md AND the apps/www site) and updates them.

2026-07-2018

lastlight-client

nearform/lastlight

Install the `lastlight` CLI and connect it as a CLIENT to an existing Last Light server — log in, save the token, and verify the connection. Use when the user wants to "connect / point my lastlight CLI at a server", "log in to Last Light", "set up the lastlight client", or run lastlight commands against a remote instance. For standing up the server itself use lastlight-server; for editing a deployment's config use lastlight-overlay.

2026-07-1918

lastlight-debug

nearform/lastlight

Debug a running Last Light instance over its admin API with the `lastlight` CLI — no SSH. Use when the user wants to "look at / debug a failed or stuck workflow", "why didn't the bot do X", "check a bad agent run / phase error on <instance>", "tail a session", "search the logs", "read the server/docker logs", "list/trigger a cron", "resolve an approval", or "check stats/cost" against a deployed server. Needs a CLI already connected (see lastlight-client to log in). For standing up the server use lastlight-server; for editing config/workflows use lastlight-overlay.

2026-07-1918

lastlight-guide

nearform/lastlight

Orientation & router for the Last Light skills. Use ONLY when the user has NOT named a concrete Last Light task — i.e. they're unsure which skill/flow they need, ask "what can Last Light do / where do I start", say "help me with Last Light" with no specific goal, or want a guided tour across server / client / overlay / debug / evals. Do NOT use when the ask already names a task — "set up/deploy a server" → lastlight-server, "connect/log in my CLI" → lastlight-client, "customize a workflow/prompt/persona/config" → lastlight-overlay, "debug a failed/stuck workflow or run on an instance" → lastlight-debug, "run evals / compare models / author a case / build a PR-review dataset" → lastlight-evals, "iteratively improve an eval toward a target score" → lastlight-evals-loop: invoke that skill directly. This skill only routes and, when the goal is ambiguous, asks. Also invocable as /lastlight-guide.

2026-07-1918

lastlight-server

nearform/lastlight

Install and configure a Last Light SERVER — the GitHub maintenance agent plus its docker-compose stack — on a host. Use when the user wants to "set up / install / deploy / stand up a Last Light server or instance", configure its GitHub App, models, managed repos, or domain, or get the agent running for the first time. Drives the `lastlight` CLI; for connecting an existing CLI to a server use lastlight-client instead, and for editing a running deployment's config use lastlight-overlay.

2026-07-1918

lastlight-evals-loop

nearform/lastlight

Drive a Last Light EVAL toward a target score with a disciplined, anti-gaming improvement loop — run → mine failures → propose candidate fix(es) → re-measure → keep the best or revert → repeat. Use when the user wants to "improve / raise the pr-review F1", "make the reviewer better against the eval", "close the loop on evals", "iterate on prompts/skills to pass more cases", or "tune the workflow to hit a score target". The loop diagnoses on a TRAIN split and validates on a BLIND held-out split so fixes must generalize, not overfit; it prefers generic overlay prompt/skill edits, and stops for human sign-off before editing any gold answer. For a one-off run/compare use lastlight-evals; to hand-fork a workflow/prompt use lastlight-overlay. Needs an already-scaffolded evals workspace (lastlight-evals) with a pr-review dataset.

2026-07-1718

name	chat
description	Conversational assistant for messaging-platform threads (Slack, Discord). Answer questions about repos, PRs, and issues, explain code, and guide users to natural-language triggers (e.g. "build owner/repo#N", "triage owner/repo", "review PRs on owner/repo", "status").

Chat

You are answering in a messaging thread (Slack, Discord). The conversation is the job — answer the question that was asked, don't expand it into a report.

What you do

Answer questions about repositories, issues, pull requests, and code.
Explain how the bot's workflows behave.
Report status on running work when asked.

What you don't do

Chat is read-and-explain only. You don't review PRs, triage issues, run builds, or change anything. When the user wants an action, name the natural-language trigger and stop:

code changes → build owner/repo#N
issue triage → triage owner/repo
PR review → review PRs on owner/repo
security scan → security review owner/repo
running-task status → status

Phrase triggers as natural language — never with a leading /, which Slack intercepts before it reaches Last Light.

Style

Concise — messaging panes are narrow. A few sentences beats a wall of text.
Markdown sparingly: bold for emphasis, fenced blocks for code.
Lead with the answer. Cite path:line when pointing at code.