Nexent Test Assets

OrganizationPopular

ModelEngine-Group

nexent-test-assets

Create and maintain Nexent's requirement-driven feature catalog, D1-D5 structured cases, change records, fixed automation, implementation manifest, generated Excel baseline, migration inventory, and Mock/Real execution declarations. Use for requirements, bug regressions, test implementation, V5 migration, or formal test-asset consistency work. Excludes the Legacy UT suite.

Overview

Publisher	ModelEngine-Group
Repository	`nexent`
Skill name	`nexent-test-assets`
Stars	5.9K
Forks	737
Bundled files	7
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
7 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ModelEngine-Group on GitHub. Read the source before you install it.

Installation

Install the Nexent Test Assets AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ModelEngine-Group/nexent/tree/develop/.agents/skills/nexent-test-assets
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/ModelEngine-Group/nexent/tree/develop/.agents/skills/nexent-test-assets

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ModelEngine-Group/nexent.git /tmp/nexent
mkdir -p .claude/skills
cp -r /tmp/nexent/.agents/skills/nexent-test-assets .claude/skills/nexent-test-assets

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Nexent Test Assets in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Nexent Test Assets on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Nexent Test Assets is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Nexent formal test assets

Maintain one traceable chain:

Requirement or Bug -> Feature -> D1-D5 Case -> Manifest -> Fixed Script -> Result.

Paths are relative to the repository root. The structured YAML/JSON files are authoritative; test/generated/Nexent_测试基线.xlsx is a deterministic read-only view.

Boundaries

Do not reuse or register tests from test/backend, test/sdk, or test/ext_components as formal D1 cases. Those are Legacy UT.
Formal scripts live only below test/automation/d1 through test/automation/d5.
Design cases before product implementation. Implement fixed scripts and manifest entries after product implementation, except an intentional bug reproduction may be written earlier.
Update only affected manifest entries, then validate the whole manifest.
Do not edit the generated Excel workbook directly.
Do not encode secrets, personal absolute paths, or environment-specific runtime IDs in formal cases or scripts.
Business tests must not depend on a specific SQL file path. Test migration behavior only at the D5 deployment boundary.
Store change records by type: requirements in test/changes/requirements/, bug fixes in test/changes/bugs/, refactors in test/changes/refactors/, and test-only fixes in test/changes/test-fixes/. Do not place change files directly below test/changes/.

Select a mode

Mode	Use	Required reference
`requirement-design`	Add or change product behavior and design D1-D5 cases	lifecycle.md, case-design.md
`bugfix`	Record a defect, explain the escaped gap, and add/reuse/strengthen regression coverage	lifecycle.md, bugfix.md
`test-implementation`	Implement fixed scripts and incrementally update the manifest	test-implementation.md, manifest.md
`migration`	Convert V5, fixed scripts, manifest, and referenced assets without changing behavior	migration.md
`mock-migration`	Add Mock/Real profiles after migration equivalence passes	mock-profiles.md

Read only the references needed for the selected mode.

Required workflow

Inspect the owning Feature, existing formal Cases, change record, manifest entries, scripts, and repository status.
Modify the authoritative YAML/JSON before regenerating derived views.
Preserve stable Feature and Case IDs. Retire instead of deleting historical contracts.
During requirement design, run python test/tools/validate_test_assets.py --phase design --generate-excel.
After fixed scripts and manifest entries exist, run python test/tools/validate_test_assets.py --phase implementation --generate-excel. Use python test/tools/generate_excel.py --check for a read-only Excel drift check.
In implementation mode, run the affected selectors and report exact results. A schema-valid asset is not execution evidence.

Status rules

active: required and executable according to its automation field.
blocked: required but missing a declared prerequisite; never count as pass.
manual: intentionally manual and not represented as automated.
skipped_by_policy: excluded by an explicit current product-test policy.
retired: historical behavior no longer executed.

A2A is in scope across D1-D5, including fixed D4 journeys. OAuth and CAS journeys remain skipped_by_policy until their policy changes.

Generated Excel layout

Generate exactly seven sheets: 00_说明, 01_功能清单, and 02_D1 through 06_D5. Each D1-D5 row includes its requirement and business-rule traceability, automation status, framework, script, selector, execution profile, Mock services, logical assets, and readable manifest validation status. Keep contract and implementation hashes in hidden trailing columns. Do not create separate automation or coverage sheets.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Nexent Test Assets AI skill do?

Why use Nexent Test Assets on TypingMind?

Because you install it once and use it with any model. Nexent Test Assets is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Nexent Test Assets in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ModelEngine-Group/nexent/tree/develop/.agents/skills/nexent-test-assets. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Nexent Test Assets?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Nexent Test Assets?

As many as you like. As long as a model supports skills, you can use Nexent Test Assets with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Nexent Test Assets AI skill free?

Yes. It is published on GitHub by ModelEngine-Group under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Nexent formal test assets

Boundaries

Select a mode

Required workflow

Status rules

Generated Excel layout

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now