Menu
Use when discovering and cloning Drupal.org projects maintained by a username.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when working on public Drupal.org Schema.org Blueprints module issues, including queue scouting, local issue tracking, issue-fork review, scoped contribution work, or assessing ecosystem impact.
Use when traversing a public Drupal.org project issue queue, maintaining local Markdown issue notes, reviewing issue forks or merge requests, or preparing scoped contribution work.
Use when working on public Drupal.org Webform module issues, including queue scouting, local issue tracking, issue-fork review, or scoped Webform contribution work.
Use when working on private Webform security issues in Drupal GitLab.
Use when cloning a known Drupal.org project machine name for local contribution work.
Use when creating logo prompt ideas for a Drupal.org module or theme.
| name | drupalorg-projects-clone |
| description | Use when discovering and cloning Drupal.org projects maintained by a username. |
Discover all projects maintained by a Drupal.org user and clone selected ones as git-backed Composer repositories. If you already know the project machine name, use drupalorg-project-clone directly.
If not provided, ask: "What is the Drupal.org username whose maintained projects you want to clone?"
Fetch https://www.drupal.org/u/{username}. Valid if the body is clearly a user profile page. On invalid (404, generic not-found body, no maintained-project area), report the problem and prompt once to retry.
Parse the maintained-project section from the profile HTML. Extract links matching /project/{machine_name}. Collect display name, machine name, and project URL. If no maintained-project section can be isolated, report a parsing failure and stop.
Fetch in parallel for every project:
https://www.drupal.org/project/{machine_name}/git-instructions — resolves project type, recommended branch, and install pathdrupalorg project:releases {machine_name} --format=llm — resolves versionVersion precedence:
-dev, -alpha, -beta, -rc)(pre-release)— with (no releases — sandbox/dev only)— with (releases unavailable)Only default to module type if Drupal.org truly does not expose it.
Display a table and wait for user input:
Projects maintained by {username}:
# Project Machine name Type Version
1. Display Name machine_name module 2.1.0
2. Another Project another_project theme 1.0.x-dev (pre-release)
3. Sandbox Thing sandbox_thing recipe — (no releases — sandbox/dev only)
Enter numbers to clone (comma-separated), or "all" to clone everything:
Accept all or comma-separated integers. Re-prompt once on invalid input. Stop on 0, none, or cancel.
Clone one at a time (Composer operations must not run in parallel — each updates shared dependency files and composer.lock).
Invoke drupalorg-project-clone with the machine name, resolved project type, and recommended branch if forcing explicitly.
Cloned N project(s):
- Display Name (machine_name, module) → web/modules/sandbox/machine_name/
drupalorg-project-clone — handles each individual project clonedrupalorg-cli — provides project:releases --format=llm