Skills tester
📦

tester

Content revision r1 Medium Risk ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables

Test React and Django Applications

Complex full-stack releases need consistent test plans and clear failure reports. This skill guides Playwright, pytest, smoke, integration, and UAT workflows for GabeDA.

Supports: Claude Codex Code(CC)
⚠️ 50 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "tester" from https://skillstore.io/skills/brownbull-tester.md and its manifest at https://skillstore.io/api/skills/brownbull-tester/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/brownbull-tester.md Signed manifest GET /api/skills/brownbull-tester/manifest Signed lockfile GET /api/skills/brownbull-tester/lockfile

Test it

Using "tester". Create smoke tests for login, dashboard access, and file upload.

Expected outcome:

  • A smoke test plan grouped by critical path and dependency.
  • Frontend and backend checks with expected outcomes.
  • A short report template for pass, fail, blocked, and follow-up items.

Using "tester". Investigate why the company switcher E2E test is failing.

Expected outcome:

  • A failure summary with observed behavior and affected workflow.
  • Likely causes such as missing test data, stale selectors, or async timing.
  • Recommended fixes and focused rerun steps.

Using "tester". Design UAT for the upload feature.

Expected outcome:

  • Business-facing acceptance scenarios for valid, invalid, and large files.
  • Required test data and stakeholder review checkpoints.
  • Exit criteria for approval or release blocking.

Security Audit

Medium Risk
v8 • 7/5/2026 Open versioned report

Most static findings are false positives from Markdown code fences, localhost URLs, relative imports, CI flags, and mocked examples. Confirmed risk remains around persistent Playwright auth storage, embedded sample credentials, and absolute output paths. No prompt injection attempt was found in the reviewed skill files.

4
Files scanned
2,270
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (2)

Medium
references/playwright-patterns.md:201-202references/test-examples.md:160-161
Hardcoded Sample Credentials
Reference examples embed testuser@gabeda.com with password gabe123123. If copied into generated tests, these values could normalize committed credentials or shared test accounts.
The same email and password strings appear directly in multiple Playwright examples. They appear to be samples, so confidence is high but not absolute.
Medium
SKILL.md:327-333
Absolute Project Paths in Output Guidance
The skill lists C:\Projects\play paths for tests, reports, strategies, and findings. Marketplace users could be directed to write outside the active workspace.
The absolute Windows paths are explicit in the skill output guidance. They may be project notes, but they create a clear risk for unintended filesystem writes.
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
references/playwright-patterns.md:243
Hidden file access
await page.context().storageState({ path: 'tests/.auth/user.json' });
The Playwright storageState example writes and reuses tests/.auth/user.json, which can contain cookies or tokens. This is a real exposure risk if generated tests commit or retain that file without safeguards.
Medium
references/playwright-patterns.md:261
Hidden file access
storageState: 'tests/.auth/user.json',
The Playwright storageState example writes and reuses tests/.auth/user.json, which can contain cookies or tokens. This is a real exposure risk if generated tests commit or retain that file without safeguards.

Risk Factors

⚙️ External commands (47)
references/playwright-patterns.md:479-481 references/playwright-patterns.md:488-490 references/playwright-patterns.md:526-539 SKILL.md:35-45 SKILL.md:45-54 SKILL.md:54-64 SKILL.md:64-68 SKILL.md:68-86 SKILL.md:86-93 SKILL.md:93-95 SKILL.md:95-100 SKILL.md:100-105 SKILL.md:105-111 SKILL.md:111-117 SKILL.md:117-124 SKILL.md:124-142 SKILL.md:142-148 SKILL.md:148-158 SKILL.md:158-169 SKILL.md:169-172 SKILL.md:172-183 SKILL.md:183-189 SKILL.md:189-190 SKILL.md:190-217 SKILL.md:217-223 SKILL.md:223-247 SKILL.md:247-254 SKILL.md:254-264 SKILL.md:264-266 SKILL.md:266-269 SKILL.md:269-272 SKILL.md:272-275 SKILL.md:275-302 SKILL.md:302-303 SKILL.md:303-304 SKILL.md:304-305 SKILL.md:305-327 SKILL.md:327-328 SKILL.md:328-331 SKILL.md:331-332 SKILL.md:332-333 SKILL.md:333-338 SKILL.md:338-347 SKILL.md:347-350 SKILL.md:350-359 SKILL.md:359-362 SKILL.md:362-371
🌐 Network access (22)
references/playwright-patterns.md:318 references/playwright-patterns.md:46 references/playwright-patterns.md:154 references/playwright-patterns.md:200 references/playwright-patterns.md:236 references/playwright-patterns.md:282 references/playwright-patterns.md:306 references/playwright-patterns.md:333 references/playwright-patterns.md:524 references/playwright-patterns.md:536 references/playwright-patterns.md:557 references/playwright-patterns.md:580 references/playwright-patterns.md:524 references/pytest-patterns.md:494 references/pytest-patterns.md:496 references/pytest-patterns.md:500 references/test-examples.md:157 references/test-examples.md:174 references/test-examples.md:191 references/test-examples.md:219 references/test-examples.md:243 references/test-examples.md:434
📁 Filesystem access (3)
references/playwright-patterns.md:220 references/playwright-patterns.md:243 references/playwright-patterns.md:261
🔑 Env variables (8)
references/playwright-patterns.md:551 references/playwright-patterns.md:552 references/playwright-patterns.md:553 references/playwright-patterns.md:581 references/playwright-patterns.md:551 references/playwright-patterns.md:552 references/playwright-patterns.md:553 references/playwright-patterns.md:581
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/brownbull-tester/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/brownbull-tester/security.svg)](https://skillstore.io/skills/brownbull-tester?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/brownbull-tester?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/brownbull-tester/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/brownbull-tester.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Brownbull. (2026). tester security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brownbull-tester/audits/8

BibTeX citation

@techreport{brownbull-brownbull-tester-2026, author = {Brownbull}, title = {tester security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/brownbull-tester/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "tester security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "Brownbull" date-released: "2026-07-05" url: "https://skillstore.io/skills/brownbull-tester/audits/8" identifiers: - type: other value: "skillstore:brownbull-tester:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
0xSero Recommended

0xsero-tester

Skillstore Score 77
Evidence Confidence High
Skillstore usage 23
Updated

2026-08-21

Brownbull Current

brownbull-tester

Skillstore Score 50
Evidence Confidence High
Skillstore usage 13
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
45
Architecture
85
Maintainability
87
Content
75
Community
83
Spec Compliance

What You Can Build

Plan release validation

Create a balanced test strategy that covers smoke checks, UAT scenarios, integration risks, and release reporting.

Add feature tests

Generate Playwright and pytest cases for a new React and Django workflow before code review.

Triage failing suites

Turn frontend and backend test failures into clear findings, likely causes, and recommended next actions.

Try These Prompts

Create a smoke test checklist 
Create a smoke test checklist for the GabeDA login, dashboard, company creation, upload, and reporting paths.
Write Playwright coverage 
Write Playwright test cases for the company switcher flow. Include setup data, assertions, and cleanup notes.
Build backend pytest cases 
Create pytest coverage for the file upload API. Include valid uploads, invalid formats, authorization checks, and edge cases.
Analyze a failed release run 
Review these frontend and backend test results. Identify root causes, missing coverage, and a prioritized remediation plan.

Best Practices

  • Use isolated test accounts, fixtures, and cleanup for every generated test.
  • Prefer stable role, label, or test ID selectors over brittle CSS or index selectors.
  • Record failures with reproduction steps, expected behavior, actual behavior, and owner-ready recommendations.

Avoid

  • Do not copy sample passwords or tokens into committed tests.
  • Do not rely on fixed waits when Playwright can wait for state or responses.
  • Do not write reports or tests outside the active workspace without explicit approval.

Frequently Asked Questions

What applications is this skill designed for?
It is designed for GabeDA, a React frontend and Django backend application.
Can it run tests automatically?
It can run documented local commands when dependencies, services, and user permissions are available.
Does it create both frontend and backend tests?
Yes. It covers Playwright browser tests and pytest coverage for Django components.
Where does it place reports?
It uses the project testing report folders described by the skill, preferably as workspace-relative paths.
Does it replace QA review?
No. It prepares tests and reports, but stakeholders must review UAT results and release decisions.
How should credentials be handled?
Use test-only fixtures or environment-provided values, and avoid committing passwords, tokens, or browser storage files.

Developer Details

Author

Brownbull

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Brownbull/khujta_ai_business/tree/main/.claude/skills/tester

Ref

5ab1d37e83436c6eef84de88573e142b94f2a4ad

Maintenance freshness

7/18/2026

Usage

11 downloads · 501 views

File structure

📁 references/

📄 playwright-patterns.md

📄 pytest-patterns.md

📄 test-examples.md

📄 SKILL.md

More from Brownbull

View all

Related Skills

View all