Skills functionality-audit

📦

functionality-audit

Name: functionality-audit
Author: DNYoussef

Content revision r1 Safe

Verify Code Functionality

Generated code can appear correct while still failing under real inputs. This skill guides Claude, Codex, or Claude Code through sandbox testing, debugging, and evidence-based reporting.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

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

Agent request

Review the Skillstore skill "functionality-audit" from https://skillstore.io/skills/dnyoussef-functionality-audit.md and its manifest at https://skillstore.io/api/skills/dnyoussef-functionality-audit/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/dnyoussef-functionality-audit.md Signed manifest GET /api/skills/dnyoussef-functionality-audit/manifest Signed lockfile GET /api/skills/dnyoussef-functionality-audit/lockfile

Test it

Using "functionality-audit". Audit a new data parser before merging it.

Expected outcome:

The report lists tested input types, expected outcomes, actual outcomes, three passing cases, one malformed-input failure, and a recommended validation fix.

Using "functionality-audit". Investigate an intermittent checkout failure.

Expected outcome:

The audit reproduces the failure under concurrent requests, identifies a race in state updates, and recommends a focused regression test.

Using "functionality-audit". Check a release candidate for deployment readiness.

Expected outcome:

The summary states the pass rate, critical defects, unresolved risks, and targeted follow-up tests needed before release.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

The static findings are false positives caused by prose about systematic testing and a DOT graph edge. I found no prompt injection, malware intent, data exfiltration, or instructions to perform unauthorized reconnaissance.

Files scanned

315

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

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

Copy report link

https://skillstore.io/skills/dnyoussef-functionality-audit/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/dnyoussef-functionality-audit.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

DNYoussef. (2026). functionality-audit security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dnyoussef-functionality-audit/audits/8

BibTeX citation

@techreport{dnyoussef-dnyoussef-functionality-audit-2026,
  author = {DNYoussef},
  title = {functionality-audit security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/dnyoussef-functionality-audit/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: "functionality-audit security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "DNYoussef"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dnyoussef-functionality-audit/audits/8"
identifiers:
  - type: other
    value: "skillstore:dnyoussef-functionality-audit:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Validate Generated Code

Run focused tests after AI code generation to prove the implementation works with representative inputs.

Debug Unclear Failures

Reproduce failures, inspect execution paths, and identify root causes before applying fixes.

Prepare Release Checks

Perform final execution verification and document risks before shipping a change.

Try These Prompts

Run Basic Verification

Use the functionality-audit skill on these files. Confirm the code runs, test the main expected behavior, and report any failures with reproduction steps.

Test Edge Cases

Audit this implementation with normal inputs, boundary values, malformed inputs, and empty inputs. Compare actual behavior against the expected behavior I provide.

Debug a Failing Feature

Use functionality-audit to reproduce this failure, identify the first incorrect behavior, explain the root cause, and propose a minimal fix with regression tests.

Verify a Release Candidate

Perform a full functionality audit for this release candidate. Create an isolated environment, run realistic tests, summarize pass and fail results, rank discovered bugs, and list remaining release risks.

Best Practices

Provide expected behavior, representative inputs, and known edge cases before the audit starts.
Run tests in an isolated environment that mirrors important production assumptions.
Use audit results to add regression tests for every confirmed bug.

Avoid

Assuming code works because it compiles or passes lint checks.
Changing code before reproducing the failure and understanding the root cause.
Testing only the easiest happy path while ignoring errors and boundaries.

Frequently Asked Questions

Does this skill write production code?

It can recommend or help verify fixes, but its main purpose is testing, debugging, and reporting.

Can it use existing test suites?

Yes. It can run existing tests and add focused cases when current coverage is incomplete.

Does it require a sandbox?

A sandbox is strongly preferred because it reduces risk from side effects during execution.

What information should I provide?

Provide file paths, expected behavior, test data, dependencies, and any known failure symptoms.

Can it audit cloud integrations?

Yes, when safe emulators, mocks, or non-production cloud resources are available.

How is this different from static analysis?

Static analysis inspects code structure. This skill runs code and compares actual behavior with expected behavior.

Developer Details

Author

DNYoussef

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/functionality-audit

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

5 downloads · 175 views

File structure

📄 functionality-audit-process.dot

📄 SKILL.md