datalust/seqcli/building-seq-plug-in-apps
Claude Code and agent skill by datalust/seqcli
- community
Checking that the SKILL.md file is still in the repository.
Use this when developing plug-in Seq inputs (for ingestion) and outputs (for alert notifications or streamed events).
Install
npx vskill@latest install datalust/seqcli/building-seq-plug-in-appsSKILL.md
This skill covers building Seq apps (plugins) using the Seq.Apps runtime API. Seq apps are .NET libraries that extend Seq with custom event processing (output apps) or event generation (input apps).
Project structure
A Seq app follows this layout:
Input apps use Seq.Input.{Name} naming.
.csproj conventions
Embedded resources for default templates use LogicalName for clean resource stream access:
Test projects target the latest stable .NET release, and use xUnit.
The runtime pins its own copies of Seq.Apps, Serilog, and Seq.Syntax — the app's copies of these assemblies are ignored at load time. Other dependencies are loaded from the app's package.
Namespace disambiguation
Projects named Seq.App.{Name} have a root namespace that collides with Seq.Apps. Use global:: where Seq.Apps.App or Seq.Apps.Host is referenced as a type within a Seq.App.* namespace:
Use InternalsVisibleTo in the main project to expose internal constructors and types to the test project.
App class structure
Output apps (event subscribers)
Output apps derive from SeqApp and implement ISubscribeToAsync<LogEvent>:
The SeqApp attribute's Name parameter is the display name in Seq's UI. Keep it short (1-3 words). Description is a single sentence shown below the name.
Output apps using raw JSON (ISubscribeToJsonAsync)
Apps that don't need Serilog LogEvent deserialization can implement ISubscribeToJsonAsync instead. This receives each event as a raw CLEF JSON string, skipping LogEvent/MessageTemplate/LogEventProperty construction entirely:
Prefer ISubscribeToJsonAsync for apps that forward or transform events without rendering human-readable output (exporters, relays, bridges), especially at high volume. It avoids the Serilog dependency entirely. The trade-off is that the Event<LogEvent> wrapper (Id, EventType, Timestamp) and Seq.Syntax template rendering are not available; the app must extract CLEF fields (@t, @l, @mt, @x, etc.) from the JSON directly.
Stick with ISubscribeToAsync<LogEvent> when the app renders human-readable output using Seq.Syntax templates (emails, chat messages, tickets) or inspects structured property values using the Serilog type system (ScalarValue, SequenceValue, StructureValue).
Input apps (event publishers)
Input apps implement IPublishJson:
The app must synchronize writes to inputWriter so that events are not interleaved (e.g., use a lock when multiple background threads produce events).
Lifecycle
- Seq instantiates the app using the public parameterless constructor
- The runtime sets
[SeqAppSetting]properties via reflection, matched by property name Attach()is called, makingApp,Host, andLogavailableOnAttached()runs — validate settings and initialize here- For subscribers:
OnAsync()is called for each matching event - For publishers:
Start()is called, thenStop()on shutdown Dispose()if implemented
Each app instance runs as a separate seqcli process. Initialization, event dispatch, and disposal are single-threaded. Events are dispatched one at a time — if OnAsync() is slow, backpressure is applied naturally. Apps may create their own background threads for ingestion.
App settings
Settings are public properties on the app class decorated with [SeqAppSetting]. They appear in Seq's UI for the user to configure. The runtime injects values by matching on the property name (not DisplayName), using Enum.Parse for enum types and Convert.ChangeType for everything else.
SeqAppSetting attribute properties
| Property | Type | Purpose | |
|---|---|---|---|
DisplayName | string | User-facing label in the UI. If omitted, the property name is used. | |
HelpText | string | Descriptive text shown to the user. Should explain the setting's purpose and give examples. | |
IsOptional | bool | If true, the user can leave the field blank. Non-optional settings that are missing cause a startup error before Attach() is called. | |
InputType | SettingInputType | Controls the UI input widget: Text, LongText, Checkbox, Integer, Decimal, Password. If Unspecified, the runtime chooses based on the property type. | |
Syntax | string | Syntax highlighting in the UI. "template" for fields accepting Seq template expressions (in {braces}), "code" for structured values (JSON, headers). Omit for plain values. | |
IsInvocationParameter | bool | Marks settings that can be overridden per-invocation (e.g., destination address, channel). |
Quality guidelines for settings
Display names should be concise, title-case-ish, and match how users think about the concept:
| Good | Avoid | |
|---|---|---|
| Bot token | BotToken | |
| Chat ID | Telegram Chat Identifier | |
| Silent notification | DisableNotification | |
| Body is plain text | BodyIsPlainText | |
| Connection security | ProtocolSecurity |
Help text should:
- Start with a clear description of the setting's purpose
- Include concrete examples where helpful (e.g., format strings, URL patterns, expected values)
- Mention defaults explicitly (e.g., "The default is
Etc/UTC.", "The default isPOST.") - Use backticks for code/values in help text
- Note when template syntax is supported: "Template syntax is supported."
- For password/token fields, explain how to obtain the value
Enum settings
When a setting has a fixed set of valid values, use an enum type. The runtime presents enum settings as a dropdown and handles validation automatically. Apply [Description] to enum members to control the dropdown text when the member name doesn't read naturally:
Setting validation
Validate required settings in OnAttached() and throw ArgumentException with a message that names the setting using its display name in backticks:
Gateway pattern (testability)
External I/O (HTTP APIs, SMTP, cloud services) is abstracted behind an interface so tests can run without network access.
The app class has dual constructors:
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingsrc/SeqCli/Skills/Resources/building-seq-plug-in-apps/SKILL.md
Popularity
- Repository stars
- 168
- Repository forks
- 30
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/datalust/seqcli/building-seq-plug-in-apps)