Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

webjs-list-todos

Sterne103

Forks69

Aktualisiert15. Juni 2026 um 18:48

Use this skill when the user asks what work is open or pending on the webjsdev/webjs project board. Trigger phrases include "what are the current todo items", "what's pending", "list todos", "what's open", "what should I work on", "show me the open issues", "any open work for webjs", "what's in progress", "what's on the board", or any natural-language query about open items on the webjs project at https://github.com/orgs/webjsdev/projects/1. The skill calls `gh project item-list` and returns a bucketed view (Todo / In progress / Done) so the user sees the current state straight from the source of truth.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

webjsdev

webjsdev/webjs

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	webjs-list-todos
description	Use this skill when the user asks what work is open or pending on the webjsdev/webjs project board. Trigger phrases include "what are the current todo items", "what's pending", "list todos", "what's open", "what should I work on", "show me the open issues", "any open work for webjs", "what's in progress", "what's on the board", or any natural-language query about open items on the webjs project at https://github.com/orgs/webjsdev/projects/1. The skill calls `gh project item-list` and returns a bucketed view (Todo / In progress / Done) so the user sees the current state straight from the source of truth.
when_to_use	Examples that should trigger this skill: "what are the current todo items" "what's pending" "list webjs todos" "what should I work on next" "show me the open issues" "any open work on the webjs board" "what's in progress right now" Do NOT trigger for: starting work on a specific issue (webjs-start-work handles that), filing a new task (webjs-file-issue handles that), or asking about closed/done items only (those are queryable but not the primary intent of this skill).

List open work on the webjs project board

The webjsdev/webjs project tracks work on the GitHub Project at https://github.com/orgs/webjsdev/projects/1. This skill returns a current snapshot bucketed by Status, queried straight from GitHub. Do NOT consult internal task trackers or memory for this question.

Steps

Fetch the board state.

gh project item-list 1 --owner webjsdev --format json

Bucket by Status (Todo, In progress, Done) and pretty-print each bucket with issue numbers and titles. If the user explicitly asked for only one bucket (e.g. "what's in progress"), filter accordingly.
Default presentation. Show Todo and In progress always. Show Done only if the user asks for it, or if both Todo and In progress are empty.
For each item, show: #<number> <title>. Wrap in markdown so the user can click through.

Example output shape

Todo:
  #112  Elide browser download of display-only component modules
  #113  Ship pre-built dist/ alongside src/ for @webjsdev/core
  #114  Rate-limit defaultKey trusts unverified X-Forwarded-For

In progress:
  (none)

If everything is in Done or the board is empty, say so explicitly.

What this skill does NOT do

Does not move cards, file new issues, or open PRs. Those are sibling skills (webjs-start-work, webjs-file-issue).
Does not show closed issues outside the project board.
Does not consult ~/.claude/projects/.../memory/ or any internal task tracker.

Failure handling

If gh returns an auth error: surface it directly to the user and suggest gh auth refresh -s project.
If the project list is empty: report "Project board is empty" instead of fabricating items.

Mehr aus diesem Repository

gleiches Repository

webjs-instagram-post

webjsdev/webjs

Publish an SEO post to the WebJs Instagram account (@webjs_dev). Use this skill whenever the user asks to post to Instagram, publish an Instagram post, share something on Instagram, or promote a page/feature/blog on Instagram for SEO. Every post is strictly for SEO reach, so every post MUST ship a freshly created branded image plus a keyword-rich caption. The skill holds the account id, the credential location, the image recipe, the public-hosting requirement, and the two-step publish flow. It never prints or commits the access token.

2026-07-22103

webjs

webjsdev/webjs

Build and review WebJs applications. Use when working on WebJs app structure, pages, layouts, routes, server actions, components, signals, data and validation, auth, sessions, styling, the client router, streaming, or tests. WebJs is AI-first, web-components-first, and has no build step.

2026-07-22103

webjs-scaffold-sync

webjsdev/webjs

Use this skill whenever a change affects what `webjs create` GENERATES (a new or changed gallery/showcase demo, a new template, a changed generated file like the layout/home/theme/schema, a new convention that belongs in generated apps, a new scaffold-shipped config/hook) OR when the user asks to sync the scaffold, "update all three templates", check the scaffold is consistent, or teach agents how to use webjs through the scaffold. The scaffold is webjs's PRIMARY teaching surface for AI agents, so a change to it must propagate in lockstep across the generators, the per-agent rule files, the scaffold tests, the framework docs that describe the scaffold, and the preview/example apps. This skill is the authoritative map of every scaffold surface plus the change-type to surface mapping, and the mandatory "generate + boot + check" verification, so no surface is silently skipped. Complements webjs-doc-sync (which owns framework API/behaviour docs); this skill owns what the scaffold emits.

2026-07-22103

webjs-start-work

webjsdev/webjs

Use this skill when the user asks to start work on a tracked GitHub issue in the webjsdev/webjs project. Trigger phrases include "work on

2026-07-22103

webjs-blog-write

webjsdev/webjs

Use this skill whenever the task is to write, draft, or substantially edit a webjs blog post (a marketing/engineering post under the repo-root `blog/` directory that the website publishes). It carries the author's voice, the hard prose rules (no em-dashes, no internal PR/issue numbers, no process tells), the SEO-first topic and front-matter conventions, the de-duplication check against every existing post, and the mandatory dogfood verification of every factual claim before a feature post ships. Invoke it BEFORE writing any blog prose so the post lands in the house voice and does not need a later cleanup pass.

2026-07-13103

webjs-doc-sync

webjsdev/webjs

Use this skill whenever a change ships a user-facing or agent-facing surface (a new export, CLI flag, package.json webjs.* config key, html hole prefix, lifecycle hook, convention, or a behaviour change to an already-documented feature) and the docs must be brought in sync, OR when the user asks to find documentation drift / doc gaps / "did we update the docs", audit shipped work for missing docs, or sync the docs surfaces. The skill carries the authoritative map of EVERY doc surface webjs ships and the change-type to surface mapping, so no surface (the docs site, the marketing website, the skill at `.agents/skills/webjs/`, README, AGENTS.md, the scaffold templates' per-agent rule files) is silently skipped.

2026-07-13103

name	webjs-list-todos
description	Use this skill when the user asks what work is open or pending on the webjsdev/webjs project board. Trigger phrases include "what are the current todo items", "what's pending", "list todos", "what's open", "what should I work on", "show me the open issues", "any open work for webjs", "what's in progress", "what's on the board", or any natural-language query about open items on the webjs project at https://github.com/orgs/webjsdev/projects/1. The skill calls `gh project item-list` and returns a bucketed view (Todo / In progress / Done) so the user sees the current state straight from the source of truth.
when_to_use	Examples that should trigger this skill: "what are the current todo items" "what's pending" "list webjs todos" "what should I work on next" "show me the open issues" "any open work on the webjs board" "what's in progress right now" Do NOT trigger for: starting work on a specific issue (webjs-start-work handles that), filing a new task (webjs-file-issue handles that), or asking about closed/done items only (those are queryable but not the primary intent of this skill).

List open work on the webjs project board

Steps

Fetch the board state.

gh project item-list 1 --owner webjsdev --format json

Bucket by Status (Todo, In progress, Done) and pretty-print each bucket with issue numbers and titles. If the user explicitly asked for only one bucket (e.g. "what's in progress"), filter accordingly.
Default presentation. Show Todo and In progress always. Show Done only if the user asks for it, or if both Todo and In progress are empty.
For each item, show: #<number> <title>. Wrap in markdown so the user can click through.

Example output shape

Todo:
  #112  Elide browser download of display-only component modules
  #113  Ship pre-built dist/ alongside src/ for @webjsdev/core
  #114  Rate-limit defaultKey trusts unverified X-Forwarded-For

In progress:
  (none)

If everything is in Done or the board is empty, say so explicitly.

What this skill does NOT do

Does not move cards, file new issues, or open PRs. Those are sibling skills (webjs-start-work, webjs-file-issue).
Does not show closed issues outside the project board.
Does not consult ~/.claude/projects/.../memory/ or any internal task tracker.

Failure handling

If gh returns an auth error: surface it directly to the user and suggest gh auth refresh -s project.
If the project list is empty: report "Project board is empty" instead of fabricating items.