Agent skill · Audited from source
Test Execution
skill · echoVic/boss-skillMIT licenceAudited 15 Oct 2026 · source 0317d4cb4f54
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 0317d4cb4f54 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 测试执行方法,包含测试框架检测、测试运行、结果解析
Cite
Cite this page
ModelsAtlas. “Test Execution (echoVic/boss-skill)”. Retrieved 15 Oct 2026. https://modelsatlas.com/skills/echovic/test-execution
Trust audit
Audit 0.4.1 · source read 15 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 0317d4cb4f54 · 15 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- PublisherechoVic GitHub userOwner of the repository this skill is read from
- Source folderechoVic/boss-skill/skill/skills/qa/test-executionThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict0317d4cb4f54A new audit runs when the source changes
- Repository statusNot archivedLast push 4 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: 测试执行方法,包含测试框架检测、测试运行、结果解析
--- name: qa/test-execution description: 测试执行方法,包含测试框架检测、测试运行、结果解析 version: 1.0.0 agent: qa type: methodology user-invocable: false agent-invocable: true dependencies: - shared/tech-stack-detection triggers: - 需要执行测试时 - 需要验证测试覆盖率时 metadata: internal: true --- # 测试执行方法 ## 强制要求:真实执行测试 **你必须真正执行测试,禁止生成 Mock 数据!** ## 测试执行流程 1. **检测项目类型和测试框架** 2. **根据项目类型执行测试** 3. **执行 E2E / 集成测试** 4. **解析测试输出**(总数、通过数、失败数、覆盖率) ## 测试框架检测 ### JavaScript/TypeScript - Jest: `jest.config.js`, `"jest"` in package.json - Vitest: `vitest.config.js`, `"vitest"` in package.json - Playwright: `playwright.config.js` - Cypress: `cypress.json` ### Python - pytest: `pytest.ini`, `"pytest"` in dependencies - unittest: 内置 ### Go - `*_test.go` 文件 ## 测试命令 | 语言 | 单元测试 | E2E测试 | |------|----------|---------| | Node.js | `npm test` | `npx playwright test` | | Python | `pytest` | `pytest tests/e2e` | | Go | `go test ./...` | - | ## Playwright E2E 执行细节 > **完整方法论**:详见 `Skill(skill: "qa/e2e-playwright")` ### 检测 Playwright 项目 检查以下标志确认项目使用 Playwright: - `playwright.config.ts` 或 `playwright.config.js` 存在 - `package.json` 中包含 `@playwright/test` 依赖 - `e2e/` 或 `tests/e2e/` 目录存在 ### 执行命令 ```bash # 安装浏览器(首次或 CI 环境) npx playwright install --with-deps # 运行全部 E2E 测试 npx playwright test # 仅 critical 标签(门禁加速) npx playwright test --grep @critical # 指定浏览器 npx playwright test --project=chromium # JSON 报告(门禁解析用) npx playwright test --reporter=json ``` ### 结果解析 Playwright JSON 报告关键字段: | 字段 | 说明 | |------|------| | `stats.expected` | 通过的测试数 | | `stats.unexpected` | 失败的测试数 | | `stats.flaky` | 重试后通过的测试数 | | `stats.skipped` | 跳过的测试数 | ### 失败排查 ```bash # 查看 trace(失败时自动生成) npx playwright show-trace <trace.zip路径> # 打开 HTML 报告 npx playwright show-report ```
Excerpt, first 1,749 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 0317d4c
git clone https://github.com/echoVic/boss-skill git -C boss-skill checkout 0317d4cb4f54
The author documents no install command, so this uses the repository directly. Our verdict covers commit 0317d4cb4f54 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
0317d4cb4f54
Similar skills
All testing skills →echoVic/boss-skill
后端API开发方法论,包括RESTful/GraphQL设计、请求验证、错误处理和安全实现
echoVic/boss-skill
系统架构设计方法论,包含架构模式选择、系统分层、目录结构设计
echoVic/boss-skill
需求澄清 Skill。当用户只给了模糊描述时自动触发,通过业务提问把一句话翻译成完整需求,交给 Boss 流水线执行。
echoVic/boss-skill
自动生成 CHANGELOG,基于 git 提交历史和 pipeline 产物信息,遵循 Conventional Commits 和 Keep a Changelog 规范
echoVic/boss-skill
代码审查方法,包含审查清单、常见问题、最佳实践
echoVic/boss-skill
竞品调研和分析方法,通过系统性分析竞品的功能、体验和策略,发现差异化机会
Questions about Test Execution
What does the Test Execution skill do?
Is Test Execution safe to install?
What can Test Execution access on my machine?
How current is this page?
Sources
- github.com/echoVic/boss-skill/tree/main/skill/skills/qa/test-exe — the audited source at commit 0317d4cb4f54 and every finding aboveObserved · 15 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Test Execution skill do?
- Is Test Execution safe to install?
- What can Test Execution access on my machine?