Deepseek Automation
zhu1090093659/deepseek-pp
A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.
Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server.
$ npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Marve10s/Better-Fullstack better-fullstack --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Marve10s/Better-Fullstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/better-fullstack .claude/skills/better-fullstack && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "better-fullstack" agent skill from https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstack into .claude/skills/better-fullstack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "better-fullstack", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstackType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Marve10s/Better-Fullstack better-fullstack --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Marve10s/Better-Fullstack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/better-fullstack .agents/skills/better-fullstack && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "better-fullstack" agent skill from https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstack into .agents/skills/better-fullstack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "better-fullstack", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Marve10s/Better-Fullstack better-fullstack --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Marve10s/Better-Fullstack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/better-fullstack .cursor/skills/better-fullstack && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "better-fullstack" agent skill from https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstack into .cursor/skills/better-fullstack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "better-fullstack", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Marve10s/Better-Fullstack.git --path .agents/skills/better-fullstack--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Marve10s/Better-Fullstack better-fullstack --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Marve10s/Better-Fullstack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/better-fullstack .gemini/skills/better-fullstack && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "better-fullstack" agent skill from https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstack into .gemini/skills/better-fullstack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "better-fullstack", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Marve10s/Better-Fullstack better-fullstackInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Marve10s/Better-Fullstack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/better-fullstack .github/skills/better-fullstack && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "better-fullstack" agent skill from https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstack into .github/skills/better-fullstack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "better-fullstack", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Marve10s/Better-Fullstack better-fullstack --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Marve10s/Better-Fullstack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/better-fullstack .opencode/skills/better-fullstack && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "better-fullstack" agent skill from https://github.com/Marve10s/Better-Fullstack/tree/main/.agents/skills/better-fullstack into .opencode/skills/better-fullstack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "better-fullstack", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
better-fullstackScaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server.
Better Fullstack is an agent skill from Marve10s/Better-Fullstack. Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server. Use when a user asks to create, generate, or scaffold a fullstack starter; choose a Better Fullstack stack; add Better Fullstack capabilities; compare agent scaffolding paths; or avoid hand-authoring boilerplate project files.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Project scaffolding. It works with Model Context Protocol, React and TypeScript. The repository describes itself as: Scaffold production-ready full-stack apps in TypeScript, Rust, Python, Go, and Java with a visual builder and CLI. Choose your frontend, backend, database, auth, AI, payments… The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b03f092. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Better Fullstack loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 582 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Marve10s/Better-Fullstack at commit b03f092, republished under its MIT licence (© Marve10s). 582 words, ~1,452 tokens.
.claude/skills/better-fullstack/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Use the Better Fullstack generator as the source of truth for starter generation. Do not hand-write a full starter when a trusted Better Fullstack interface can produce it.
Use an already-available CLI by default. The benchmarked best framing is: map the stack, dry-run the CLI, then run the same non-interactive command for real.
Use MCP only when the user explicitly asks for MCP, when CLI access is unavailable, or when the request needs structured schema lookup beyond what a concise CLI command can safely express. If using MCP, start with bfs_get_guidance, then use schema, compatibility, plan, and create/add tools in that order.
Use a trusted Better Fullstack interface in this order:
PATH.If none is available, ask the user for the command, service, tool, or docs source they want used. Do not invent a bootstrap command.
--dry-run.--dry-run.create <project-name> --part ... for explicit or multi-ecosystem stacks.--no-install --no-git for agent-driven scaffolding unless the user explicitly asks for side effects.--package-manager bun when the user or project expects Bun.--ai-docs agents-md for reusable projects, or --ai-docs none for benchmarks and throwaway scaffolds.none explicitly for categories the user wants disabled.frontend:typescript:react-vitebackend:typescript:honobackend.runtime:typescript:bundatabase:universal:sqlitebackend.orm:typescript:drizzlebackend.api:typescript:trpcfrontend.css:typescript:tailwindfrontend.ui:typescript:daisyuibackend.logging:typescript:pinocodeQuality:universal:biomeUse graph parts as category:ecosystem:option.
<better-fullstack-cli> create my-app \
--part frontend:typescript:react-vite \
--part backend:typescript:hono \
--part database:universal:sqlite \
--part backend.runtime:typescript:bun \
--part backend.api:typescript:trpc \
--part backend.orm:typescript:drizzle \
--part frontend.css:typescript:tailwind \
--part frontend.ui:typescript:daisyui \
--part backend.logging:typescript:pino \
--part codeQuality:universal:biome \
--forms none \
--validation none \
--ai-docs none \
--package-manager bun \
--no-install \
--no-git<better-fullstack-cli> create api-app \
--part backend:python:fastapi \
--part database:universal:postgres \
--part backend.orm:python:sqlmodel \
--part backend.validation:python:pydantic \
--part backend.auth:python:jwt \
--part codeQuality:python:ruff \
--ai-docs agents-md \
--no-install \
--no-gitFor a generated project with bts.jsonc, use the Better Fullstack add command or MCP add tools. Use canonical Stack Part specs so each capability keeps its category and owner, for example:
<better-fullstack-cli> add --project-dir ./my-app --part staticAnalysis:typescript:knip --part workspaceRunner:universal:turborepo --no-installFor MCP lifecycle work, use this sequence:
bfs_get_project_status reads configuration and manifest prerequisites without running
toolchains or writing files.bfs_check_project runs every generated target check. It requires installed dependencies and
required toolchains; missing prerequisites are failures. It does not rewrite Better Fullstack
source/configuration directly, though build tools may fetch dependencies and write locks,
caches, compiler output, or build artifacts.bfs_plan_project_update reads current-template drift. It returns a reviewToken only when a
supported manifest-v1 baseline exists and all exact structured-merge content fits the 32 KiB
per-file MCP review bound. Oversized content is withheld with size/SHA metadata and no token.bfs_apply_project_update with acknowledgeUnprovenManifestV1: true. Missing, stale,
cross-project, or bounded-review-ineligible tokens fail closed. Apply destructively overwrites
currently actionable template files and advances the v1 manifest without installing dependencies.Manifest v1 does not prove generator release/SHA provenance or cross-version eligibility, and the current apply path has no transactional backup or automated recovery. Do not promise those Wave 1 guarantees.
Report the command or tool path used, any compatibility adjustments, the project directory, and the next install/test/run commands. Do not claim dependencies are installed when --no-install or MCP creation skipped them.
© Marve10s, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .agents/skills/better-fullstack of Marve10s/Better-Fullstack.
Open the folder on GitHubat commit b03f092
Better Fullstack next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Better Fullstack this skillMarve10s/Better-Fullstack | 752 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Deepseek Automationzhu1090093659/deepseek-pp | 1.9k | — | ~2.1k | Automated safety check: Notes | Apache-2.0 | |
| Code Reviewnteract/semiotic | 2.7k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Agentbro PR Mergeshirenchuang/agentbro | 203 | — | ~648 | Automated safety check: Pass | Apache-2.0 | |
| Pixijs Createpixijs/pixijs-skills | 346 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Dynamo Webview Component ScaffoldDynamoDS/Dynamo | 2k | — | ~991 | Automated safety check: Pass | Apache-2.0 |
zhu1090093659/deepseek-pp
A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
shirenchuang/agentbro
A skill your agent uses when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution…
pixijs/pixijs-skills
A skill your agent uses when scaffolding a new PixiJS v8 project with the create-pixi CLI or adding PixiJS to an existing project.
DynamoDS/Dynamo
Scaffolds a new Dynamo package repo that hosts a view extension with a WebView2-embedded React frontend.
holaboss-ai/holaOS
Builds new holaOS apps with @holaboss/app-builder-sdk, either as integration-only MCP modules or as dashboard apps with a shadcn UI under src/client/.
Marve10s/Better-Fullstack
Animation components and utilities for Remotion video projects.
Marve10s/Better-Fullstack
Create Remotion videos using the Geist design system aesthetic.
Marve10s/Better-Fullstack
Create modern product launch/pitch videos using Remotion. An agent skill from Marve10s/Better-Fullstack.
Marve10s/Better-Fullstack
Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic.
Marve10s/Better-Fullstack
Add capabilities, addons, deployment targets, generated CI, services, or stack updates to an existing Better Fullstack project.
Marve10s/Better-Fullstack
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack.
Works with
Categories
Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server. Better Fullstack is an agent skill from Marve10s/Better-Fullstack. Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server.
Better Fullstack fits situations like: A user asks to create; scaffold a fullstack starter; choose a Better Fullstack stack; add Better Fullstack capabilities.
Run `npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a claude-code`. Or copy the skill folder (.agents/skills/better-fullstack in Marve10s/Better-Fullstack) into .claude/skills/better-fullstack in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a codex`. Or copy the skill folder (.agents/skills/better-fullstack in Marve10s/Better-Fullstack) into .agents/skills/better-fullstack in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Marve10s/Better-Fullstack --skill better-fullstack -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/better-fullstack, .gemini/skills/better-fullstack, .github/skills/better-fullstack and .opencode/skills/better-fullstack in your project.
SKILL.md names no scripts, command-line tools or credentials: Better Fullstack is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Better Fullstack is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Better Fullstack: Deepseek Automation (zhu1090093659/deepseek-pp, 1.9k stars), Code Review (nteract/semiotic, 2.7k stars), Agentbro PR Merge (shirenchuang/agentbro, 203 stars) and Pixijs Create (pixijs/pixijs-skills, 346 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Marve10s (a GitHub user) maintains it in Marve10s/Better-Fullstack, which has 752 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: Marve10s/Better-Fullstack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.