How do I install the Downstream E2e skill?

Run npx skillmds@latest add shakacode/downstream-e2e 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.

What does the Downstream E2e skill do?

Run downstream integration checks through scripts/e2e/downstream.sh when it exists, or report the current #59 blocker stub. It is listed under Docs & Writing on SkillMD.

Is Downstream E2e safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Downstream E2e?

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 Downstream E2e free to use?

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

Who published Downstream E2e?

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

Downstream E2e by shakacode — Agent Skill

Name: Downstream E2e
Author: shakacode

File contents

Downstream E2E

Use this skill when validating react-on-rails-rsc against a downstream app or consumer fixture.

Current Status

This skill is currently a documented stub because scripts/e2e/downstream.sh does not exist on origin/main as of the issue #67 setup work.

Blocker: #59

Do not claim a downstream e2e pass from this skill while the script is missing.

When The Script Exists

From the repository root:

bash scripts/e2e/downstream.sh "$@"

If the script provides --help, read it first and follow the script's current interface. The exact downstream app selection interface is UNKNOWN until #59 lands.

Expected Workflow

Read AGENTS.md for the current validation policy.
Confirm scripts/e2e/downstream.sh exists:
```
test -f scripts/e2e/downstream.sh
```
If the script prints its own usage with --help, prefer that interface over this stub text.
Run the downstream script with the requested arguments.
Report the exact command, package version or local package source tested, downstream target, and result.
If the script is missing, report the #59 blocker and do not substitute an ad hoc downstream smoke test.

Stub Output

When the script is still missing, report:

BLOCKED downstream-e2e: scripts/e2e/downstream.sh is not present. Track #59 before using downstream e2e as a merge or release gate.

Frequently asked questions

Downstream E2e