Skills Guide

Weline Framework Runtime

VerifiedSafe

Skill for managing Weline Framework runtime and WLS processes: worker, dispatcher, maintenance, session server, and debugging.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
7/27/2026
Claude Code
#wls-runtime#process-orchestration#php-framework#server-reload#session-server

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Automated summary

Guides runtime and process work in WelineFramework — workers, dispatcher, lifecycle, maintenance mode — inside a given DEV-workspace repository.

Strengths

  • Prescribes an explicit reading order (runtime-basics, session-runtime) before making changes
  • Gives a clear reload-versus-restart rule based on the kind of change being made
  • Flags request-level static state as a WLS hazard and requires verifying its reset behavior
  • Directs reviews to inspect worker, dispatcher, orchestrator, maintenance, and health-check paths together

Limitations

  • Tightly coupled to specific repository paths (E:\WelineFramework\DEV-workspace), so it is not portable as-is
  • Does not spell out commands or diagnostic procedures, relying on external reference files instead
  • Assumes prior familiarity with WLS concepts such as Worker, Dispatcher, and StateManager
When to use it

Use it whenever a task involves starting, reloading, restarting, or debugging WelineFramework WLS processes.

When not to use it

Avoid it for business-code or feature work unrelated to runtime, workers, or maintenance mode.

Security analysis

Safe
Quality score80/100

This is a documentation-only skill that provides runtime guidance for WelineFramework. It references local repo files and safe framework commands such as server:reload, with no destructive actions, secret exfiltration, obfuscation, or instructions to disable safety controls.

No concerns found

How this analysis is made

Examples

Reload after a business-code change
I changed a controller in the WelineFramework business module — should I run server:reload or server:restart, and what do I need to check afterwards?
Static state leak under WLS
Under WLS my service returns stale data between requests. Inspect the worker, dispatcher and StateManager reset paths and tell me whether request-level static state is leaking.
Maintenance mode and session server
Help me put the WLS runtime into maintenance mode safely and confirm the Session Server and health-check paths behave correctly before I reload the workers.

name: weline-framework-runtime description: Use for WelineFramework runtime and WLS work: worker, dispatcher, reload/restart, maintenance mode, process orchestration, state reset, session server, memory service, and runtime debugging. Trigger when the task mentions WLS, Worker, Dispatcher, server:start, server:reload, server:restart, maintenance, Session Server, StateManager, or process lifecycle issues.

Weline Framework Runtime

Use this skill for runtime/process work in E:\WelineFramework\DEV-workspace.

Read in this order

  1. references/runtime-basics.md
  2. references/session-runtime.md if Session/Auth is involved
  3. Repo references when needed: dev/ai/skills/runtime-and-process/SKILL.md dev/ai/skills/session-development/SKILL.md dev/ai/rules/wls-state-management.mdc

Defaults

  • For business-code changes, prefer php bin/w server:reload
  • Use restart only when changing startup parameters, Master/Dispatcher flow, or other reload-insufficient runtime pieces
  • Treat request-level static state as suspicious under WLS and verify reset behavior
  • When reviewing WLS issues, inspect worker, dispatcher, orchestrator, maintenance, and health-check paths together

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/weline-framework-runtime-ms2s7dos/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/weline-framework-runtime-ms2s7dos' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/weline-framework-runtime-ms2s7dos/download' --output '.skill-downloads/weline-framework-runtime-ms2s7dos/SKILL.md.part' && mv '.skill-downloads/weline-framework-runtime-ms2s7dos/SKILL.md.part' '.skill-downloads/weline-framework-runtime-ms2s7dos/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/weline-framework-runtime-ms2s7dos/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot