Skip to content
cccskills

Results for “daemon”

137 skills · sorted by relevance

Daemon

FreeSummary

Build and maintain a public profile from LifeOS goals, projects, ideas, and work themes. Rule-based filters remove sensitive details, while preview and approval workflows let you review changes before deploying the profile site.

  • Refresh a public profile from LifeOS activity
  • Review profile changes before publishing
  • Check the current profile section by section
danielmiessler/LifeOS19.5KUpdated Sep 4, 2026

Build daemon/background processes that start on boot, run continuously, and manage their own lifecycle. Covers macOS launchd (plist files, agents vs daemons), Linux systemd (unit files), Windows services, process supervision, logging, health checks, graceful shutdown, auto-restart, and AI-powered daemons that manage LLM API connections and rate limits. Activate on: "daemon", "background process", "launchd", "systemd", "service file", "plist", "launch agent", "launch daemon", "auto-start", "always running", "process supervisor", "pm2", "background service", "boot service", "AI daemon", "long-running process". NOT for: container orchestration (use devops-automator), cron jobs that run and exit (use task-scheduler), web server deployment (use backend-architect).

The English summary is being prepared. Showing the original description.

curiositech/windags-skills16Updated Oct 14, 2026

Build daemon/background processes that start on boot, run continuously, and manage their own lifecycle. Covers macOS launchd (plist files, agents vs daemons), Linux systemd (unit files), Windows services, process supervision, logging, health checks, graceful shutdown, auto-restart, and AI-powered daemons that manage LLM API connections and rate limits. Activate on: "daemon", "background process", "launchd", "systemd", "service file", "plist", "launch agent", "launch daemon", "auto-start", "always running", "process supervisor", "pm2", "background service", "boot service", "AI daemon", "long-running process". NOT for: container orchestration (use devops-automator), cron jobs that run and exit (use task-scheduler), web server deployment (use backend-architect).

The English summary is being prepared. Showing the original description.

curiositech/port-daddy3Updated Oct 18, 2026

yao-daemon

FreeSummary

Start and manage long-running background services such as development servers. Check their status and output logs, verify listening ports, retrieve local URLs, and restart services while keeping the same service ID.

  • Starting a development server in the background
  • Checking service status and output logs
  • Restarting a service while keeping its ID
YaoApp/yao8.1KUpdated Oct 18, 2026

組織を中断し、broker daemon まで含めて完全に停止する。 「完全に止める」「daemon ごと落とす」「org down して」「全部終了」と言われたときに使う。 suspend(状態保存 + ja 管理プロセス / ペイン停止)を完走してから `claude-org-runtime org down` を呼ぶ統合終了。単に「中断」「今日は終わり」なら daemon を残す /org-suspend を使う。

The English summary is being prepared. Showing the original description.

suisya-systems/claude-org-ja5Updated Oct 19, 2026

Fix intermittent `{:no_translation, :unicode, :latin1}` crashes in Elixir escript daemons that use length-prefixed framed IPC on stdin/stdout. Use when: (1) daemon worker crashes only on some input files, usually ones with non-ASCII bytes (kanji, cyrillic, emoji); (2) error surfaces as `Protocol error` from daemon's error branch or as garbled frame-length bytes seen by the orchestrator/client side; (3) standalone one-shot mode works fine on the same input but multi-request daemon mode fails; (4) `IO.binread(:stdio, N)` returns `{:error, {:no_translation, :unicode, :latin1}}` despite the "bin" prefix suggesting it should be encoding-agnostic. Root cause is the escript default `:standard_io` encoding — it's `:unicode`, and `IO.binread` still routes through the io_server, which translates bytes to codepoints and errors when raw binary frames contain invalid UTF-8 sequences.

The English summary is being prepared. Showing the original description.

Disentinel/grafema35Updated Aug 24, 2026

Grida AI agent system work: `@grida/daemon` (DaemonServer, loopback HTTP perimeter, files/workspaces, secrets store, daemon discovery) and `@grida/agent` (the agent tenant: sessions, providers/BYOK, runtime/tool execution, skills discovery, prompts, tiers, sandbox hosts). Use for `packages/grida-daemon/**`, `packages/grida-ai-agent/**`, desktop sidecar protocol changes, agent chat transport, and bugs in agent state or streams. For pure Electron window, preload, menu, deep-link, or CDP work, use `desktop`.

The English summary is being prepared. Showing the original description.

gridaco/grida2.7KUpdated Oct 15, 2026

Harden the Docker daemon by configuring daemon.json with user namespace remapping, TLS authentication, rootless mode, and CIS benchmark controls.

The English summary is being prepared. Showing the original description.

MustafaKemal0146/fetih5Updated Oct 11, 2026

Guide changes to OpenRig itself by locating relevant source files, choosing tests, assessing sensitive areas, and preparing pull requests. Use isolated test environments to check changes without disrupting the daemon running the current agent session.

  • Locate the source files responsible for a behavior
  • Choose tests for an OpenRig change
  • Test without disrupting the current agent session
mvschwarz/openrig7.8KUpdated Oct 19, 2026

gwm

Free

Manage git worktrees across any repository with the `gwm` Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (`gwm exec`) or reclaim build artifacts (`gwm clean`), materialise a PR into a worktree (`gwm review`), drive a multi-repo workspace (`--workspace`), run the JSON daemon / statusline (`gwm daemon`, `gwm statusline`), list or pin AI-agent sessions per worktree (`gwm agents`, Claude Code / Codex / opencode / Mistral Vibe detection), seed config from a preset (`gwm init --preset`), diagnose with `gwm doctor`, drive tmux/zellij, or wire `gcd` via `gwm shell-init`. Also covers multi-forge (#419): GitHub via `gh` **or** GitLab via `glab`, the `forge` / `[forge_hosts]` keys, and `gwm trust add`. Triggers on `gwm`, `gwq`, `git worktree`, `.gwm.toml`, `forge`, `forge_hosts`, `glab`, `gwm trust add`, GitLab MR, `gwm create`, `gwm list`, `gwm exec`, `gwm clean`, `gwm review`, `gwm daemon`, `gwm statusline`, `gwm agents`, `gwm note`, `gwm bootstrap`, `gwm doctor`, `gwm switch`, `gwm tmux`, `gwm zellij`, `gwm link`, `gwm status`, `gwm shell-init`, `gcd`, `feat/#`, `fix/#`, GitHub issue/PR linking on a worktree.

The English summary is being prepared. Showing the original description.

kbrdn1/gwm-cli148Updated Oct 17, 2026

Print the localhost URL for The Luminarium — moflo's daemon dashboard — for the current project. Use when the user asks for "the luminarium link", "the moflo dashboard", "the daemon UI", or anything synonymous. Each project gets a deterministic port in 33000–33999; the actual bound port is recorded in `.moflo/daemon.lock`.

The English summary is being prepared. Showing the original description.

eric-cielo/moflo19Updated Oct 18, 2026

Audits an Articles of Agreement contract — the daemon-witnessed agreement every official Port Daddy agent signs covering registration, transcript reporting, tool-use gating, file claims, parley conduct, budget limits, and operator control — against the enforcement-beats-hope bar: a clause counts as safe only when it resolves to a concrete, daemon-observable mechanism with a defined denial shape, never a promise the agent might honor. Use when drafting a new agent's Articles, reviewing a compliance-level (C0-C6) claim, deciding whether a clause is genuinely enforced or merely documented, or auditing whether an agent's claimed identity can be trusted. NOT for securing the inbound event-to-spawn path (fleet-event-spawn-trust), designing the relay's transport PKI and signing keys (pd-relay-zero-trust), or tracking an agent's identity and reputation across its whole lifetime after it signs (agent-identity-continuity-reputation).

The English summary is being prepared. Showing the original description.

curiositech/port-daddy3Updated Oct 18, 2026

Verify every visual-evidence artifact (screenshot/GIF/recording) attached to a PR carries a provenance manifest binding it to real daemon-backed truth — daemon port, run id, transcript head hash, agent node id, commit, and an honest real/fixture/mock source label — and that operator-control-panel PRs cover the required set of proof states. Use when gating a PR's proof artifacts before merge, auditing whether a "LIVE" visual claim is backed by a real daemon run versus a reused or fixture-backed mock, or defining the required state-coverage set for a control-panel change. NOT for the capture technique itself — headless Playwright, `screencapture -x -l`, non-interruptive capture (use port-daddy-agent-skill's visual-evidence doctrine), designing the receipt body schema an artifact attaches to (use agent-work-receipt-designer), or the broader dogfood/Potemkin product-quality bar (use multi-agent-authoring-product-bar).

The English summary is being prepared. Showing the original description.

curiositech/port-daddy3Updated Oct 18, 2026

ruflo-doctor

FreeSummary

Check a Ruflo installation for common environment and configuration problems, then run automatic repairs. The checks cover software versions, background services, the memory database, API keys, MCP servers, disk space, and TypeScript.

  • Checking the environment after installing Ruflo
  • Diagnosing configuration and connection problems
  • Repairing the memory database
ruvnet/ruflo76.8KUpdated Oct 19, 2026

Set up and run kube-bench to check Kubernetes configuration against CIS security benchmarks. Select the appropriate benchmark and cluster components, then export JSON or JUnit results for automated pipelines and troubleshoot skipped checks or incorrect detection.

  • Setting up kube-bench for the first time
  • Selecting benchmark versions and scan targets
  • Exporting JSON or JUnit results for CI
mukul975/Anthropic-Cybersecurity-Skills34.7KUpdated Aug 31, 2026

openrig-user

FreeSummary

Look up exact syntax, options, JSON output, defaults, and error meanings for a known OpenRig command. Use the reference to check command behavior and diagnose runtime differences against the installed help and running daemon.

  • Checking required flags for a known rig command
  • Looking up queue commands and handoff syntax
  • Investigating command errors and daemon compatibility
mvschwarz/openrig7.8KUpdated Oct 19, 2026

c-review

FreeSummary

Review native C/C++ applications and services for memory errors, integer overflows, and race conditions, where concurrent operations interfere. Coordinate multiple reviewers and produce findings with severity ratings, alongside reports of missing or unverified review coverage.

  • Audit a native C/C++ application for security flaws
  • Review a daemon or service for memory safety
  • Investigate integer overflows and race conditions
trailofbits/skills7.6KUpdated Oct 16, 2026

Check claude-ops background daemon end-to-end and auto-fix common issues. Detects stale plist paths after plugin upgrades, missing service commands, dead processes, corrupt health files, and bash version mismatches.

The English summary is being prepared. Showing the original description.

davepoon/buildwithclaude3.7KUpdated Oct 19, 2026

Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to Fluent Bit from the DPU}, {daemon starts but no schema rows appear}. This skill owns the CollectX collection mechanism plus the operator's own doca-telemetry / doca-telemetry-exporter usage; it ROUTES the productized DOCA Telemetry Service (DTS) to public docs (AGENTS.md Non-goal #7), the reader API to doca-telemetry, and the publisher API to doca-telemetry-exporter. Refuse to invent clx symbols, provider names, schema fields, flags, or config paths — describe the class and route to the live source.

The English summary is being prepared. Showing the original description.

NVIDIA/skills3.6KUpdated Oct 18, 2026

Use claudraband CLI and daemon workflows programmatically to send prompts, resume sessions, inspect status, and manage live session state. Use when running, scripting, or automating Claude Code via claudraband/`cband`, including startup prompt handling, `--connect` daemon mode, and ACP sessions.

The English summary is being prepared. Showing the original description.

halfwhey/claudraband288Updated Apr 19, 2026

Complement to alice-emacs-mods. Covers what alice does not — ghostel mastery, multi-daemon orchestration, cross-session coordination, debug/recovery harness, REPL-as-dynamical-citizen, QRTP distribution, strobe internals, and the hard-won lessons from spawning and debugging live REPLs under the server daemon. Read alongside alice-emacs-mods; together they tile the total Emacs-mod space on this machine.

The English summary is being prepared. Showing the original description.

plurigrid/asi70Updated Jul 10, 2026

Stop the Telegram channel daemon.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Exploit misconfigured Docker environments, specifically focusing on privilege escalation via an exposed Docker daemon socket (`docker.sock`) or membership in the local `docker` user group to achieve root access on the host system.

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

Schedule a moflo spell to run on the local machine via the moflo daemon (cron, interval, or one-time). Use when the user wants to schedule, automate, or recurringly run one of THEIR spells locally — e.g. "schedule the oap spell every hour", "run my audit spell every weekday at 9am", "fire X once tomorrow morning". This is the LOCAL daemon path. For remote Anthropic-cloud agents, use /schedule instead.

The English summary is being prepared. Showing the original description.

eric-cielo/moflo19Updated Oct 18, 2026