How do I install the Feature Verify skill?

Run npx skillmds@latest add majiayu000/feature-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Feature Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Feature Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Feature Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Feature Verify?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Feature Verify by majiayu000 — Agent Skill

Name: Feature Verify
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Feature Verification Skill

Trigger

Keywords: verify, investigate, diagnose, check if working, anomaly, validate
User provides credentials for data sources

When NOT to Use

Need to modify data (this skill is read-only only)
Pure code review (use codex-review)
Feature development (use feature-dev)

Core Principle

ALL OPERATIONS MUST BE READ-ONLY

Claude independent analysis -> Form conclusion -> Codex third-perspective confirmation -> Integrated report

Workflow

Phase 1: Explore    -> Understand system architecture, data flow, trigger points
Phase 2: Plan       -> Build verification checklist, present to user for confirmation
Phase 3: Execute    -> Execute read-only queries, record expected vs actual
Phase 4: Analyze    -> Claude independently forms diagnostic conclusion
Phase 5: Confirm    -> /codex-brainstorm third-perspective verification
Phase 6: Integrate  -> Synthesize dual perspectives, produce final report

Safety Rules

Rule	Description
READ-ONLY	No write/update/delete operations allowed
PLAN-FIRST	Present verification plan before executing queries
CREDENTIAL-SAFETY	Do not expose full credentials in output
INDEPENDENT-FIRST	Claude forms conclusion first, then asks Codex to confirm

Verification Checklist

Category	Checks
Feature Checks	API endpoints, jobs, error handling
Data Checks	Collections, aggregations, external
Integration Checks	End-to-end flow

Verification

Report includes Executive Summary + Status
Each check has expected/actual/status
Both Claude + Codex perspectives are documented
Recommendations split into Immediate / Further / Long-term

References

references/queries.md - Query templates + safety rules
references/output-template.md - Report format

Examples

Input: /feature-verify User Auth
       MongoDB: mongodb://...
       {ANALYTICS}: project_id={PROJECT_ID}
Action: Explore -> Plan -> Execute queries -> Analyze -> Codex confirm -> Report

Input: verify user auth is working correctly
Action: Phase 1-6 flow -> Output diagnostic report

---name: feature-verifydescription: System diagnosis skill (READ-ONLY). Verifies feature behavior through code analysis, data validation, and Codex deep confirmation. All operations are strictly read-only - NO data modification allowed.--- # Feature Verification Skill ## Trigger - Keywords: verify, investigate, diagnose, check if working, anomaly, validate - User provides credentials for data sources ## When NOT to Use - Need to modify data (this skill is read-only only) - Pure code review (use codex-review) - Feature development (use feature-dev) ## Core Principle ``` ALL OPERATIONS MUST BE READ-ONLY ``` ``` Claude independent analysis -> Form conclusion -> Codex third-perspective confirmation -> Integrated report ``` ## Workflow ``` Phase 1: Explore -> Understand system architecture, data flow, trigger points Phase 2: Plan -> Build verification checklist, present to user for confirmation Phase 3: Execute -> Execute read-only queries, record expected vs actual Phase 4: Analyze -> Claude independently forms diagnostic conclusion Phase 5: Confirm -> /codex-brainstorm third-perspective verification Phase 6: Integrate -> Synthesize dual perspectives, produce final report ``` ## Safety Rules | Rule | Description | | ----------------- | ------------------------------------------------ | | **READ-ONLY** | No write/update/delete operations allowed | | PLAN-FIRST | Present verification plan before executing queries | | CREDENTIAL-SAFETY | Do not expose full credentials in output | | INDEPENDENT-FIRST | Claude forms conclusion first, then asks Codex to confirm | ## Verification Checklist | Category | Checks | | ------------------ | ----------------------------------- | | Feature Checks | API endpoints, jobs, error handling | | Data Checks | Collections, aggregations, external | | Integration Checks | End-to-end flow | ## Verification - Report includes Executive Summary + Status - Each check has expected/actual/status - Both Claude + Codex perspectives are documented - Recommendations split into Immediate / Further / Long-term ## References - `references/queries.md` - Query templates + safety rules - `references/output-template.md` - Report format ## Examples ``` Input: /feature-verify User Auth MongoDB: mongodb://... {ANALYTICS}: project_id={PROJECT_ID} Action: Explore -> Plan -> Execute queries -> Analyze -> Codex confirm -> Report ``` ``` Input: verify user auth is working correctly Action: Phase 1-6 flow -> Output diagnostic report ```

Frequently asked questions

Feature Verify