remix
Build and Review Remix 3 Applications
Remix 3 application changes require version-specific APIs and component patterns that differ from React and Remix 2. This skill guides documentation checks, focused implementation, and behavior verification using existing application conventions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "remix" from https://skillstore.io/skills/remix-run-remix.md and its manifest at https://skillstore.io/api/skills/remix-run-remix/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.
Test it
Using "remix". Explain the request flow for the greeting route.
Expected outcome:
- The route contract defines the GET endpoint and its name parameter.
- The controller returns a plain greeting response using the matched parameter.
- The router maps that contract to the controller and receives requests from the runtime adapter.
- The same route contract generates links to the endpoint.
Using "remix". Review a counter that appears on the page but does not respond to clicks.
Expected outcome:
- Check that the component is mounted or hydrated in the browser.
- Confirm that the click handler changes local state and requests another render.
- Read changing props during rendering instead of capturing their initial values.
- Verify the click interaction in a browser; rendered HTML alone does not establish interactivity.
Security Audit
SafeAll 23 static findings are false positives involving Markdown formatting, TypeScript examples, a local route dispatcher, or a fixed relative import. No evidence found of prompt injection, credential exfiltration, or unsafe command execution. The skill recommends protecting browser-visible modules and testing rejection paths.
Risk Factors
โ๏ธ External commands (21)
๐ Network access (1)
๐ Filesystem access (1)
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.
Copy report link
https://skillstore.io/skills/remix-run-remix/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/remix-run-remix?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/remix-run-remix?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/remix-run-remix/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/remix-run-remix.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
remix-run. (2026). remix security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/remix-run-remix/audits/1BibTeX citation
@techreport{remix-run-remix-run-remix-2026,
author = {remix-run},
title = {remix security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/remix-run-remix/audits/1},
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: "remix security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "remix-run"
date-released: "2026-10-12"
url: "https://skillstore.io/skills/remix-run-remix/audits/1"
identifiers:
- type: other
value: "skillstore:remix-run-remix:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Add a Typed Application Route
Connect a new route contract, controller, and router mapping using installed APIs and the existing application structure.
Review an Interactive Component
Check local state, changing props, browser hydration, and event handling without applying React-specific assumptions.
Verify a Structural Refactor
Preserve runtime and middleware conventions while checking tests, typechecking, diagnostics, and failure paths.
Try These Prompts
Inspect this Remix 3 app and explain its routes, router, and controllers. Check installed documentation before describing unfamiliar APIs.
Add a GET route for [feature] using this app's route contracts and controller conventions. Verify imports against installed documentation and run relevant checks.
Investigate [component] for stale props or missing browser interaction. Use Remix component patterns and verify both ordinary document behavior and the enhanced path.
Review [change] for middleware order, access control, and browser-visible secrets. Test rejection paths and report unverified behavior. Run diagnostics after structural changes.
Best Practices
- Check installed documentation before choosing APIs, imports, or component patterns.
- Preserve existing application conventions and change the narrowest module responsible for the behavior.
- Run relevant checks, exercise browser interactions, and report failure paths or behavior that remain unverified.
Avoid
- Apply React hooks, Remix 2 conventions, or newer online APIs without checking the installed version.
- Expose secrets or trusted server logic through browser-reachable modules.
- Run destructive database commands or rewrite configuration solely to clear diagnostics.