Agent skill

Run Tests

by runceel in runceel/ReactiveProperty

Runs .NET tests with dotnet test. An agent skill from runceel/ReactiveProperty.

MITAuto-check passedTesting & QA

Install Run Tests

skills CLI
$ npx skills add runceel/ReactiveProperty --skill run-tests -a claude-code

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

GitHub CLI
$ gh skill install runceel/ReactiveProperty run-tests --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/runceel/ReactiveProperty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-tests .claude/skills/run-tests && 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/

Facts

Skill name
run-tests
GitHub stars
944
Token cost
~3.6k tokens
SKILL.md length
1,498 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Runs .NET tests with dotnet test. An agent skill from runceel/ReactiveProperty.

  • Works in 3 steps: Detect the test platform and framework → Run tests → Run filtered tests
  • User says run tests
  • SKILL.md covers When to Use, When Not to Use, Inputs and Critical Rules — Avoid…, plus 4 more sections
  • Calls dotnet

What it does

Run Tests is an agent skill from runceel/ReactiveProperty. Runs .NET tests with dotnet test. Use when user says "run tests", "run my tests", "run these tests", "execute tests", "dotnet test", "test filter", "filter by category", "filter by class", "combine filters", "run only specific tests", "integration tests", "unit tests", "tests not running", "hang timeout", "blame-hang", "blame-crash", "crash dump", "TRX report", "TRX", "test report", "generate TRX", "TUnit", "treenode-filter", "target framework", "multi-TFM", or needs to detect the test platform (VSTest or…

Its SKILL.md is about 3.6k 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 Testing & QA, covering Unit testing, Test generation and Failing and flaky tests. It works with .NET. The repository describes itself as: ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions. Target frameworks are .NET 6+, .NET Framework 4.7.2 and .NET Standard 2.0. The licence is MIT.

When your agent uses it

  • User says run tests
  • Run these tests
  • Filter by category
  • Filter by class

Example prompts

  • “run tests”
  • “run my tests”
  • “run these tests”
  • “/run-tests”

Workflow steps

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

  1. Detect the test platform and framework
  2. Run tests
  3. Run filtered tests

What it can do on your machine

Read from SKILL.md and the folder at commit e7e6474. 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

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Run Tests loads about 3.6k tokens when it runs. Until then it costs about 245 tokens; SKILL.md has 1,498 words of instructions outside code blocks.

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

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

The full file from runceel/ReactiveProperty at commit e7e6474, republished under its MIT licence (© runceel). 1,498 words, ~3,635 tokens.

Download SKILL.mdSave it as .claude/skills/run-tests/SKILL.md (or your agent's skills folder).
name
run-tests
description
Runs .NET tests with dotnet test. Use when user says "run tests", "run my tests", "run these tests", "execute tests", "dotnet test", "test filter", "filter by category", "filter by class", "combine filters", "run only specific tests", "integration tests", "unit tests", "tests not running", "hang timeout", "blame-hang", "blame-crash", "crash dump", "TRX report", "TRX", "test report", "generate TRX", "TUnit", "treenode-filter", "target framework", "multi-TFM", or needs to detect the test platform (VSTest or Microsoft.Testing.Platform), identify the test framework, apply test filters, or troubleshoot test execution failures. Covers MSTest, xUnit, NUnit, and TUnit across both VSTest and MTP platforms. Also use for --filter-class, --filter-trait, --report-trx, --logger trx, --blame-hang-timeout, and other platform-specific filter and reporting syntax. DO NOT USE FOR: writing or generating test code, CI/CD pipeline configuration, or debugging failing test logic.
metadata.github-path
plugins/dotnet-test/skills/run-tests
metadata.github-pinned
v1.0.0
metadata.github-ref
refs/tags/v1.0.0
metadata.github-repo
https://github.com/dotnet/skills
metadata.github-tree-sha
1df99bb3ac1d06d88693057255ae159d8458ae52

Run .NET Tests

Detect the test platform and framework, run tests, and apply filters using dotnet test.

When to Use

  • User wants to run tests in a .NET project
  • User needs to run a subset of tests using filters
  • User needs help detecting which test platform (VSTest vs MTP) or framework is in use
  • User wants to understand the correct filter syntax for their setup

When Not to Use

  • User needs to write or generate test code (use writing-mstest-tests for MSTest, or general coding assistance for other frameworks)
  • User needs to migrate from VSTest to MTP (use migrate-vstest-to-mtp)
  • User wants to iterate on failing tests without rebuilding (use mtp-hot-reload)
  • User needs CI/CD pipeline configuration (use CI-specific skills)
  • User needs to debug a test (use debugging skills)

Inputs

InputRequiredDescription
Project or solution pathNoPath to the test project (.csproj) or solution (.sln). Defaults to current directory.
Filter expressionNoFilter expression to select specific tests
Target frameworkNoTarget framework moniker to run against (e.g., net8.0)

Critical Rules — Avoid Cross-Platform Mistakes

These are the most common agent mistakes. Internalize before proceeding:

RuleWhy
Do NOT use --logger trx for MTP projectsMTP uses --report-trx (requires the TrxReport extension package)
Do NOT use --report-trx for VSTest projectsVSTest uses --logger trx
Do NOT use -- --arg on .NET SDK 10+SDK 10+ passes MTP args directly: dotnet test --project . --report-trx
Do NOT omit -- on .NET SDK 8/9 with MTPSDK 8/9 requires the separator: dotnet test -- --report-trx
Do NOT use --filter "ClassName=..." with xUnit v3 on MTPxUnit v3 on MTP uses --filter-class, --filter-method, --filter-trait
Do NOT use bare positional path on SDK 10+Use --project <path> or --solution <path> instead
Do NOT use --blame for MTP projectsMTP uses --blame-crash and --blame-hang-timeout separately (each requires its extension package)
Do NOT use --collect "Code Coverage" for MTPMTP uses --coverage (requires the CodeCoverage extension package)

Workflow

Quick Reference
PlatformSDKCommand pattern
VSTestAnydotnet test [<path>] [--filter <expr>] [--logger trx]
MTP8 or 9dotnet test [<path>] -- <MTP_ARGS>
MTP10+dotnet test --project <path> <MTP_ARGS>

Detection files to always check (in order): global.json -> .csproj -> Directory.Build.props -> Directory.Packages.props

Step 1: Detect the test platform and framework
  1. Run dotnet --version in the project directory to determine the SDK version. This accounts for global.json SDK pinning.
  2. Read global.json — on .NET SDK 10+, "test": { "runner": "Microsoft.Testing.Platform" } is the authoritative MTP signal. If present, the project uses MTP and SDK 10+ syntax (no -- separator).
  3. Read .csproj, Directory.Build.props, and Directory.Packages.props for framework packages and MTP properties. Always check all three files — MTP properties are frequently set in Directory.Build.props rather than individual .csproj files.
  4. For full detection logic (SDK 8/9 signals, framework identification), see the platform-detection skill.

What to look for in each file:

FileLook forIndicates
global.json"test": { "runner": "Microsoft.Testing.Platform" }MTP on SDK 10+
global.json"sdk": { "version": "..." }SDK version (determines -- separator behavior)
.csproj<TestingPlatformDotnetTestSupport>trueMTP on SDK 8/9
.csprojMSTest, xunit.v3, NUnit, TUnit packagesFramework identity
.csprojMicrosoft.NET.Test.Sdk + test adapterVSTest (unless overridden by MTP signals above)
.csproj<TargetFrameworks> (plural)Multi-TFM — may need --framework
Directory.Build.props<TestingPlatformDotnetTestSupport>trueMTP on SDK 8/9 (often set here, not in .csproj)
Directory.Packages.propsCentrally managed test package versionsFramework identity for CPM repos

Quick detection summary:

SignalMeans
global.json has "test": { "runner": "Microsoft.Testing.Platform" }MTP on SDK 10+ — pass args directly, no --
<TestingPlatformDotnetTestSupport>true in csproj or Directory.Build.propsMTP on SDK 8/9 — pass args after --
Neither signal presentVSTest
Step 2: Run tests
VSTest (any .NET SDK version)
bash
dotnet test [<PROJECT> | <SOLUTION> | <DIRECTORY> | <DLL> | <EXE>]

Common flags:

FlagDescription
--framework <TFM>Target a specific framework in multi-TFM projects (e.g., net8.0)
--no-buildSkip build, use previously built output
--filter <EXPRESSION>Run selected tests (see Step 3)
--logger trxGenerate TRX results file
--collect "Code Coverage"Collect code coverage using Microsoft Code Coverage (built-in, always available)
--blameEnable blame mode to detect tests that crash the host
--blame-crashCollect a crash dump when the test host crashes
--blame-hang-timeout <duration>Abort test if it hangs longer than duration (e.g., 5min)
-v <level>Verbosity: quiet, minimal, normal, detailed, diagnostic
MTP with .NET SDK 8 or 9

With <TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>, dotnet test bridges to MTP but uses VSTest-style argument parsing. MTP-specific arguments must be passed after --:

bash
dotnet test [<PROJECT> | <SOLUTION> | <DIRECTORY> | <DLL> | <EXE>] -- <MTP_ARGUMENTS>
MTP with .NET SDK 10+

With the global.json runner set to Microsoft.Testing.Platform, dotnet test natively understands MTP arguments without --:

bash
dotnet test
    [--project <PROJECT_OR_DIRECTORY>]
    [--solution <SOLUTION_OR_DIRECTORY>]
    [--test-modules <EXPRESSION>]
    [<MTP_ARGUMENTS>]

Examples:

bash
# Run all tests in a project
dotnet test --project path/to/MyTests.csproj

# Run all tests in a directory containing a project
dotnet test --project path/to/

# Run all tests in a solution (sln, slnf, slnx)
dotnet test --solution path/to/MySolution.sln

# Run all tests in a directory containing a solution
dotnet test --solution path/to/

# Run with MTP flags
dotnet test --project path/to/MyTests.csproj --report-trx --blame-hang-timeout 5min

Note: The .NET 10+ dotnet test syntax does not accept a bare positional argument like the VSTest syntax. Use --project, --solution, or --test-modules to specify the target.

Common MTP flags

These flags apply to MTP on both SDK versions. On SDK 8/9, pass after --; on SDK 10+, pass directly.

Built-in flags (always available):

FlagDescription
--no-buildSkip build, use previously built output
--framework <TFM>Target a specific framework in multi-TFM projects
--results-directory <DIR>Directory for test result output
--diagnosticEnable diagnostic logging for the test platform
--diagnostic-output-directory <DIR>Directory for diagnostic log output

Extension-dependent flags (require the corresponding extension package to be registered):

FlagRequiresDescription
--filter <EXPRESSION>Framework-specific (not all frameworks support this)Run selected tests (see Step 3)
--report-trxMicrosoft.Testing.Extensions.TrxReportGenerate TRX results file
--report-trx-filename <FILE>Microsoft.Testing.Extensions.TrxReportSet TRX output filename
--blame-hang-timeout <duration>Microsoft.Testing.Extensions.HangDumpAbort test if it hangs longer than duration (e.g., 5min)
--blame-crashMicrosoft.Testing.Extensions.CrashDumpCollect a crash dump when the test host crashes
--coverageMicrosoft.Testing.Extensions.CodeCoverageCollect code coverage using Microsoft Code Coverage

Some frameworks (e.g., MSTest) bundle common extensions by default. Others may require explicit package references. If a flag is not recognized, check that the corresponding extension package is referenced in the project.

Show full SKILL.md (586 more words)Show less
Alternative MTP invocations

MTP test projects are standalone executables. Beyond dotnet test, they can be run directly:

bash
# Build and run
dotnet run --project <PROJECT_PATH>

# Run a previously built DLL
dotnet exec <PATH_TO_DLL>

# Run the executable directly (Windows)
<PATH_TO_EXE>

These alternative invocations accept MTP command line arguments directly (no -- separator needed).

Step 3: Run filtered tests

See the filter-syntax skill for the complete filter syntax for each platform and framework combination. Key points:

  • VSTest (MSTest, xUnit v2, NUnit): dotnet test --filter <EXPRESSION> with =, !=, ~, !~ operators
  • MTP -- MSTest and NUnit: Same --filter syntax as VSTest; pass after -- on SDK 8/9, directly on SDK 10+
  • MTP -- xUnit v3: Uses --filter-class, --filter-method, --filter-trait (not VSTest expression syntax)
  • MTP -- TUnit: Uses --treenode-filter with path-based syntax

Validation

  • Test platform (VSTest or MTP) was correctly identified
  • Test framework (MSTest, xUnit, NUnit, TUnit) was correctly identified
  • Correct dotnet test invocation was used for the detected platform and SDK version
  • Filter expressions used the syntax appropriate for the platform and framework
  • Test results were clearly reported to the user

Common Pitfalls

PitfallSolution
Missing Microsoft.NET.Test.Sdk in a VSTest projectTests won't be discovered. Add <PackageReference Include="Microsoft.NET.Test.Sdk" />
Using VSTest --filter syntax with xUnit v3 on MTPxUnit v3 on MTP uses --filter-class, --filter-method, etc. -- not the VSTest expression syntax
Passing MTP args without -- on .NET SDK 8/9Before .NET 10, MTP args must go after --: dotnet test -- --report-trx
Using -- --arg separator on .NET SDK 10+SDK 10+ passes MTP args directly — do NOT use -- separator
Using --logger trx for MTP or --report-trx for VSTestEach platform has its own TRX flag — check the Critical Rules table
Only checking .csproj for MTP signalsAlways check Directory.Build.props and Directory.Packages.props too — MTP properties are frequently set there
Using bare positional path argument on SDK 10+SDK 10+ requires named flags: --project <path> or --solution <path>

Troubleshooting

Common error messages and how to resolve them:

ErrorCauseFix
No test is available or No test matches the given testcase filterWrong filter syntax for the platform/framework, or tests not discoveredVerify filter syntax matches the platform (see filter-syntax skill). For discovery issues, check that the test SDK and adapter packages are installed
The --report-trx option is unrecognizedMTP extension package not referenced, or using MTP flag on a VSTest projectAdd <PackageReference Include="Microsoft.Testing.Extensions.TrxReport" /> for MTP, or use --logger trx for VSTest
The --blame-hang-timeout option is unrecognizedMissing HangDump extension on MTPAdd <PackageReference Include="Microsoft.Testing.Extensions.HangDump" />
error NETSDK1045: The current .NET SDK does not support targeting .NET X.0SDK version in global.json doesn't match the project's target frameworkUpdate global.json SDK version or install the required SDK
The test runner process exited with non-zero exit codeMTP test host crashed or test failureRun with --blame-crash (MTP) or --blame (VSTest) to collect a crash dump for diagnosis
No test source files were found / No test project founddotnet test can't find a test project in the given pathSpecify the path explicitly: dotnet test <path/to/project.csproj> (VSTest) or dotnet test --project <path> (SDK 10+)
Tests discovered but 0 executedFilter expression matches no testsDouble-check filter property names and values. Common typo: TestCategory (MSTest) vs Category (NUnit) vs trait syntax (xUnit)
Using -- for MTP args on .NET SDK 10+On .NET 10+, MTP args are passed directly: dotnet test --project . --blame-hang-timeout 5min — do NOT use -- --blame-hang-timeout
Multi-TFM project runs tests for all frameworksUse --framework <TFM> to target a specific framework
global.json runner setting ignoredRequires .NET 10+ SDK. On older SDKs, use <TestingPlatformDotnetTestSupport> MSBuild property instead
TUnit --treenode-filter not recognizedTUnit is MTP-only. On .NET SDK 10+ use dotnet test; on older SDKs use dotnet run since VSTest-mode dotnet test does not support TUnit

© runceel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/run-tests of runceel/ReactiveProperty.

Open the folder on GitHubat commit e7e6474

Compare with similar skills

Run Tests 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.

Run Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Tests this skillrunceel/ReactiveProperty944—~3.6kAutomated safety check: PassMIT
Run Testsmicrosoft/testfx1k—~4.2kAutomated safety check: PassMIT
MAUI Helix Unit Test Runnerdotnet/maui23k—~1.4kAutomated safety check: PassMIT
Blue Teamgaasher/Agent-Loop-Skills174—~3.6kAutomated safety check: PassMIT
Frappe Testing UnitImpertio-Studio/Frappe_Claude_Skill_Package187—~3kAutomated safety check: PassMIT
Debug Playwright Prowquay/quay2.8k—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • Run Tests

    microsoft/testfx

    Official

    For dotnet test: figures out which test platform (VSTest vs Microsoft.Testing.Platform) a project uses from Directory.Build.props, global.json, and .csproj, then picks the matching command syntax.

    1k GitHub stars~4.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Submits .NET MAUI unit tests to Helix queues from a local machine and monitors job status and per-work-item logs with PowerShell scripts.

    23k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Blue Team

    gaasher/Agent-Loop-Skills

    A skill your agent uses when the user has concrete failing cases in code or a guardrail/classifier/filter/prompt/API they own — a red-team failure catalogue OR a CI/CD test-failure report (failing…

    174 GitHub stars~3.6k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Frappe Testing Unit

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests.

    187 GitHub stars~3k tokensUpdated 20 days ago
    Testing & QAAuto-check passed
  • Deep-dive diagnosis of a Playwright test failure already isolated to one Quay Prow/OpenShift CI run: downloads its GCS artifacts (results.json, JUnit, build/pod logs, Jaeger traces), classifies real…

    2.8k GitHub stars~2.2k tokensUpdated today
    Testing & QAAuto-check passed
  • OpenROAD Module Test Adder

    The-OpenROAD-Project/OpenROAD

    Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.

    3.2k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

More from runceel/ReactiveProperty

All 12 skills in this repo
  • Msbuild Antipatterns

    runceel/ReactiveProperty

    Catalog of MSBuild anti-patterns with detection rules and fix recipes.

    944 GitHub stars~3.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Binlog Failure Analysis

    runceel/ReactiveProperty

    Analyze MSBuild binary logs to diagnose build failures by replaying binlogs to searchable text logs.

    944 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Coverage Analysis

    runceel/ReactiveProperty

    Automated, project-wide code coverage and CRAP (Change Risk Anti-Patterns) score analysis for .NET projects with existing unit tests.

    944 GitHub stars~5.9k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Development Workflow

    runceel/ReactiveProperty

    ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty.

    944 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Dotnet10 Features

    runceel/ReactiveProperty

    Reference for the .NET 10 / C 14 features that are relevant to the ReactiveProperty repository.

    944 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Migrate Vstest To Mtp

    runceel/ReactiveProperty

    Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP).

    944 GitHub stars~4.3k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Run Tests

What does Run Tests do?

Runs .NET tests with dotnet test. An agent skill from runceel/ReactiveProperty. Run Tests is an agent skill from runceel/ReactiveProperty.NET tests with dotnet test.

When should I use Run Tests?

Run Tests fits situations like: user says run tests; run these tests; filter by category; filter by class.

How do I install Run Tests in Claude Code?

Run `npx skills add runceel/ReactiveProperty --skill run-tests -a claude-code`. Or copy the skill folder (.agents/skills/run-tests in runceel/ReactiveProperty) into .claude/skills/run-tests in your project. Claude Code loads it when a task matches its description.

How do I install Run Tests in Codex?

Run `npx skills add runceel/ReactiveProperty --skill run-tests -a codex`. Or copy the skill folder (.agents/skills/run-tests in runceel/ReactiveProperty) into .agents/skills/run-tests in your project. Codex loads it when a task matches its description.

Can I use Run Tests 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 runceel/ReactiveProperty --skill run-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-tests, .gemini/skills/run-tests, .github/skills/run-tests and .opencode/skills/run-tests in your project.

What does Run Tests need to run?

Going by SKILL.md and its folder, Run Tests needs the command-line tools its instructions call (dotnet).

Does Run Tests 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 Run Tests 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 Run Tests use?

Run Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Tests use?

About 3.6k tokens (SKILL.md is roughly 15k 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 Run Tests?

Skills that share tags, products or a category with Run Tests: Run Tests (microsoft/testfx, 1k stars), MAUI Helix Unit Test Runner (dotnet/maui, 23k stars), Blue Team (gaasher/Agent-Loop-Skills, 174 stars) and Frappe Testing Unit (Impertio-Studio/Frappe_Claude_Skill_Package, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Tests?

runceel (a GitHub user) maintains it in runceel/ReactiveProperty, which has 944 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 31, 2026.

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