[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75XEB3CXVVF6SSR4A7DGM65":3,"skill-same:01M75XEB3CXVVF6SSR4A7DGM65":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75XEB3CXVVF6SSR4A7DGM65","project-command-handler",null,"Use when a controller action needs business logic beyond rendering or redirecting, for the command and handler pair pattern and DomainErrors.","loupe-ac\u002Floupe","loupe-ac","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F345019842?v=4","01M75XDH3V7GZDHB5M0J04BFTP","Loupe","01M75XDH4EWXVAMQEHFV5TWBMF",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-command-handler\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: project-command-handler\ndescription: \"Use when a controller action needs business logic beyond rendering or redirecting, for the command and handler pair pattern and DomainErrors.\"\n---\n\n# Command + Handler Pattern\n\nA controller action that does more than render a template or redirect uses a\ncommand + handler pair. The controller injects the handler and calls it\nsynchronously as a callable. Symfony Messenger is not involved. Do not put\nbusiness logic in a controller. Do not route a command through Messenger unless\nasync dispatch is a stated requirement.\n\n## Scope: every entry point\n\nThe pattern covers every entry point, and controllers are only one of them.\nConsole commands (`Command\u002FConsole\u002F`) and messenger handlers are thin shells too.\nThey invoke a `Command\u002F` + `Handler` pair. They never call a business-logic\nservice directly.\n\nName a domain pair verb-first, for example `RunTrialSweepCommand`. Give it a name\nthat differs from the console command class and the messenger handler class, so\nthe three never collide.\n\n`PurgeExpiredExportsCommand` injects `ExpiredExportPurger` directly. This is a\nknown pre-existing violation. Migrate it when you touch it. Do not copy it.\n\n## File layout\n\nBoth classes live in the module's `Command\u002F` directory:\n\n```\nsrc\u002FModule\u002FProject\u002FCommand\u002FCreateIssueCommand.php\nsrc\u002FModule\u002FProject\u002FCommand\u002FCreateIssueHandler.php\n```\n\nName the pair after the action: `\u003CAction>\u003CEntity>Command` \u002F `\u003CAction>\u003CEntity>Handler`.\n\n## The command carries data only\n\nWrite a `final readonly class` with public promoted constructor properties. It\nholds no logic, and no public method other than `__construct()`.\n\n```php\nfinal readonly class CreateIssueCommand\n{\n    public function __construct(\n        public Project $project,\n        \u002F** @phpstan-var non-empty-string *\u002F\n        public string $title,\n        public ?string $description,\n    ) {\n    }\n}\n```\n\n- A command may carry an entity directly. The controller resolved it through\n  route entity mapping.\n- For external-system data, carry only the stable ID. When the action imports or\n  syncs data from a third-party API, the command holds the identifier only, for\n  example `int $externalRepositoryId`. The handler fetches the full payload\n  inside `__invoke()`.\n- Do not share one command between a call site that passes magic constants and\n  one that passes real variables. Create a dedicated command for the fixed\n  invocation, a sealed-parameter command. For example, the handler of an\n  `OpenBrainstormCommand` hardcodes the seed prompt. A constructor that one\n  caller feeds string constants is a smell.\n- Pass raw input in, and parse it in the handler. Unstructured text that needs\n  parsing or normalization, such as a textarea with one item per line, travels\n  as the raw scalar string. The handler runs the parser inside `__invoke()`. Do\n  not parse in the controller and pass a pre-built array. This is the same\n  shape as the external-API rule. Every consumer of the handler (another\n  handler, a console command, a test) then gets the parsing, the dedup and the\n  normalization. The controller stays a thin request\u002Fhandler\u002Fresponse shell.\n\n  ```php\n  \u002F\u002F ✗ controller parses, command carries the result\n  new ImportItemsCommand(items: ItemsImport::parse($data->items ?? ''));\n  \u002F\u002F ✓ command carries raw text, handler parses\n  new ImportItemsCommand(items: $data->items ?? '');\n  \u002F\u002F handler __invoke(): $labels = ItemsImport::parse($command->items);\n  ```\n\n## The handler owns the business logic\n\nWrite a `final readonly class` with exactly one public method, `__invoke()`. It\ntakes the command. It returns the created or affected entity, or `void`. The\nhandler owns repository reads, persistence (`persist` + `flush`), side effects,\ndomain logging and async dispatch. A handler may dispatch a Messenger message as\na side effect. Only the command itself never goes through Messenger.\n\n```php\nfinal readonly class CreateProjectHandler\n{\n    public function __construct(\n        private ProjectRepository $projectRepo,\n        private EntityManagerInterface $em,\n    ) {\n    }\n\n    public function __invoke(CreateProjectCommand $command): Project\n    {\n        $existing = $this->projectRepo->findByOrgAndSlug($command->org, $command->slug);\n        if (null !== $existing) {\n            throw new DomainErrors(['slug' => 'project.new_project.error.slug_duplicate']);\n        }\n\n        $project = new Project($command->org, $command->name, $command->slug);\n        $this->em->persist($project);\n        $this->em->flush();\n\n        return $project;\n    }\n}\n```\n\n## Read handlers and view naming\n\nNot every handler writes. A controller action that only renders but needs data\nstill goes through a handler, because a controller may not touch a repository\ndirectly (`controller.directStateAccess`, see `project-backend`). A read\u002Fquery\nhandler follows the same shape rules: `final readonly` and a single\n`__invoke()`. It returns a view object instead of a persisted entity. A view is a\n`final readonly` DTO in the same `Command\u002F` directory.\n\nKeep a handler and its view coherent:\n\n- The view name mirrors the handler name. A `List\u003CX>Handler` returns a\n  `List\u003CX>View`, verb-first, for example `ListIssuesHandler` returns\n  `ListIssuesView`. Do not invert it to `\u003CX>ListView`.\n- The returned data contains what the handler name promises. A\n  `ShowProjectHandler` that returns a bare `list\u003CIssue>` is wrong, because the\n  name leads you to expect a `Project`. A `Show\u003CX>Handler` returns a view that\n  contains the looked-up `\u003CX>` and its related data. For example,\n  `ShowProjectHandler` returns `ProjectDetailView { public Project $project; … }`.\n  The controller then reads the entity off the view (`'project' => $view->project`),\n  and not from the route parameter separately.\n\nKeep the `Show*` family (noun-first, `ProjectDetailView`) and the `List*` family\n(verb-first, `ListIssuesView`) distinct. Match the family you extend. Do not\nunify them.\n\n## Enforced shapes (gamache PHPStan rules)\n\n`Gamache\\PHPStan\\CommandShapeRule` and `HandlerShapeRule` run under `just ci` on\nevery class in a `Command\\` namespace.\n\n- A command is a class whose name does not end in `Handler` and that has no\n  parent class. It must be `final readonly`, with no public method besides\n  `__construct()`. Identifiers: `command.notFinalReadonly`,\n  `command.hasPublicMethods`.\n- A handler is a class whose name ends in `Handler`. It must be `final readonly`,\n  with exactly one public method, `__invoke()`. Identifiers:\n  `handler.notFinalReadonly`, `handler.invalidShape`.\n- Symfony console commands extend `Symfony\\...\\Command`, so the rule skips them.\n  They live in `Command\u002FConsole\u002F`.\n\n## Calling from the controller\n\nInject the handler and invoke it as a callable. The controller only parses the\nrequest, calls the handler, handles `DomainErrors` and returns a response.\n\n```php\npublic function __construct(\n    private readonly CreateIssueHandler $createIssueHandler,\n) {\n}\n\n\u002F\u002F inside __invoke(), after $form->isValid():\n$issue = ($this->createIssueHandler)(new CreateIssueCommand(\n    project: $project,\n    title: $formRequest->title ?: throw new \\LogicException('title required after validation'),\n    description: $formRequest->description,\n));\n```\n\n## DomainErrors, the domain validation failure channel\n\n`App\\Exception\\DomainErrors` (`src\u002FException\u002FDomainErrors.php`) carries\nfield-level domain failures from the handler to the controller. Its payload is a\n`non-empty-array\u003Cstring, string>` of field name to translation key. Never throw\nit with an empty array.\n\nIn the handler, collect the failures and `throw new DomainErrors($errors)`. This\ncovers uniqueness and duplicate checks, and state preconditions such as\n\"resource already in desired state\". The handler injects the repositories it\nneeds and enforces the invariant itself. The controller must never pre-check a\ndomain rule before it calls the handler.\n\nIn the controller, catch the exception and map it onto the form. Inject\n`TranslatorInterface $translator`.\n\n```php\n} catch (DomainErrors $e) {\n    foreach ($e->errors as $field => $translationKey) {\n        $form->get($field)->addError(new FormError($this->translator->trans($translationKey)));\n    }\n}\n```\n\nThen re-render with `renderFormResponse()`, which sets HTTP 422 on a submitted\nform.\n\n## Auditing a domain event\n\nA handler records its domain event through `Ubermuda\\AuditBundle\\Auditor`. Inject\n`Auditor` and call `record()`. Do not log the same event beside the record,\nbecause the package's Monolog sink writes the log line for it. A second logger\nemits the event twice, and no assertion on the record can see that.\n\nA handler that also calls an external service, or runs a batch job, keeps its\nlogger for that call. Stripe, the async export and the site-review outbox drain\ndo this. The record answers what happened and to whom. The log line beside it\ncarries the diagnostics the trail must not hold.\n`DirectLogging::assertDiagnosticsLoggedBeside()` pins that split.\n\n```php\n$this->auditor->record(\n    'board.card_deleted',\n    AuditOutcome::Success,\n    ['cardId' => $cardId, 'projectId' => $projectId],\n    new AuditSubject('card', $cardId),\n);\n```\n\nThe operation name matches `\u002F^[a-z][a-z0-9_]*\\.[a-z][a-z0-9_]*$\u002F`. Write the\nmodule first, then one snake_case outcome phrase, and keep one namespace per\nmodule. gamache's `AuditOperationNameRule` enforces the pattern through PHPStan.\n\nRecord after the transaction commits, never inside the closure. The sink drains\nat `kernel.terminate`, so a record written inside outlives a rollback. Snapshot\nthe ids and the scalars before a delete, because the removed entity carries no\nid. Put in the context what answers a later question, such as the source status\nand the target status of a move. Keep user prose out, and record a count or a\nboolean instead. `RecordingAuditor` and `DirectLogging::assertRemovedFrom()` in\n`tests\u002FSupport\u002F` assert the record and the absent logger.\n\n## Handler composition\n\nA handler may inject another handler and call it as a callable,\n`($this->subHandler)(new SubCommand(...))`. Do this only when other call sites\nalso invoke the sub-operation. If it is only ever a sub-step, inline the logic.\n\nThe caller decides whether `DomainErrors` from the sub-handler propagates, or is\na tolerated fallback. Check the values, which are translation keys, with\n`in_array`. Re-throw anything unexpected.\n\n```php\ntry {\n    ($this->openBrainstorm)(new OpenBrainstormCommand($conversation));\n} catch (DomainErrors $e) {\n    if (!\\in_array('brainstorm.error.no_inference_key', $e->errors, true)) {\n        throw $e;\n    }\n    $this->logger->info('project.brainstorm_open_skipped', [...]);\n}\n```\n\n## Related conventions\n\nThe examples above are illustrative. The skeleton ships no concrete command\nclasses of its own. For the surrounding conventions (controllers, forms and\nDTOs, flash messages, logging), see `project-backend`. For handler tests, see\n`project-testing`.\n","# Command + Handler Pattern\n\nA controller action that does more than render a template or redirect uses a\ncommand + handler pair. The controller injects the handler and calls it\nsynchronously as a callable. Symfony Messenger is not involved. Do not put\nbusiness logic in a controller. Do not route a command through Messenger unless\nasync dispatch is a stated requirement.\n\n## Scope: every entry point\n\nThe pattern covers every entry point, and controllers are only one of them.\nConsole commands (`Command\u002FConsole\u002F`) and messenger handlers are thin shells too.\nThey invoke a `Command\u002F` + `Handler` pair. They never call a business-logic\nservice directly.\n\nName a domain pair verb-first, for example `RunTrialSweepCommand`. Give it a name\nthat differs from the console command class and the messenger handler class, so\nthe three never collide.\n\n`PurgeExpiredExportsCommand` injects `ExpiredExportPurger` directly. This is a\nknown pre-existing violation. Migrate it when you touch it. Do not copy it.\n\n## File layout\n\nBoth classes live in the module's `Command\u002F` directory:\n\n```\nsrc\u002FModule\u002FProject\u002FCommand\u002FCreateIssueCommand.php\nsrc\u002FModule\u002FProject\u002FCommand\u002FCreateIssueHandler.php\n```\n\nName the pair after the action: `\u003CAction>\u003CEntity>Command` \u002F `\u003CAction>\u003CEntity>Handler`.\n\n## The command carries data only\n\nWrite a `final readonly class` with public promoted constructor properties. It\nholds no logic, and no public method other than `__construct()`.\n\n```php\nfinal readonly class CreateIssueCommand\n{\n    public function __construct(\n        public Project $project,\n        \u002F** @phpstan-var non-empty-string *\u002F\n        public string $title,\n        public ?string $description,\n    ) {\n    }\n}\n```\n\n- A command may carry an entity directly. The controller resolved it through\n  route entity mapping.\n- For external-system data, carry only the stable ID. When the action imports or\n  syncs data from a third-party API, the command holds the identifier only, for\n  example `int $externalRepositoryId`. The handler fetches the full payload\n  inside `__invoke()`.\n- Do not share one command between a call site that passes magic constants and\n  one that passes real variables. Create a dedicated command for the fixed\n  invocation, a sealed-parameter command. For example, the handler of an\n  `OpenBrainstormCommand` hardcodes the seed prompt. A constructor that one\n  caller feeds string constants is a smell.\n- Pass raw input in, and parse it in the handler. Unstructured text that needs\n  parsing or normalization, such as a textarea with one item per line, travels\n  as the raw scalar string. The handler runs the parser inside `__invoke()`. Do\n  not parse in the controller and pass a pre-built array. This is the same\n  shape as the external-API rule. Every consumer of the handler (another\n  handler, a console command, a test) then gets the parsing, the dedup and the\n  normalization. The controller stays a thin request\u002Fhandler\u002Fresponse shell.\n\n  ```php\n  \u002F\u002F ✗ controller parses, command carries the result\n  new ImportItemsCommand(items: ItemsImport::parse($data->items ?? ''));\n  \u002F\u002F ✓ command carries raw text, handler parses\n  new ImportItemsCommand(items: $data->items ?? '');\n  \u002F\u002F handler __invoke(): $labels = ItemsImport::parse($command->items);\n  ```\n\n## The handler owns the business logic\n\nWrite a `final readonly class` with exactly one public method, `__invoke()`. It\ntakes the command. It returns the created or affected entity, or `void`. The\nhandler owns repository reads, persistence (`persist` + `flush`), side effects,\ndomain logging and async dispatch. A handler may dispatch a Messenger message as\na side effect. Only the command itself never goes through Messenger.\n\n```php\nfinal readonly class CreateProjectHandler\n{\n    public function __construct(\n        private ProjectRepository $projectRepo,\n        private EntityManagerInterface $em,\n    ) {\n    }\n\n    public function __invoke(CreateProjectCommand $command): Project\n    {\n        $existing = $this->projectRepo->findByOrgAndSlug($command->org, $command->slug);\n        if (null !== $existing) {\n            throw new DomainErrors(['slug' => 'project.new_project.error.slug_duplicate']);\n        }\n\n        $project = new Project($command->org, $command->name, $command->slug);\n        $this->em->persist($project);\n        $this->em->flush();\n\n        return $project;\n    }\n}\n```\n\n## Read handlers and view naming\n\nNot every handler writes. A controller action that only renders but needs data\nstill goes through a handler, because a controller may not touch a repository\ndirectly (`controller.directStateAccess`, see `project-backend`). A read\u002Fquery\nhandler follows the same shape rules: `final readonly` and a single\n`__invoke()`. It returns a view object instead of a persisted entity. A view is a\n`final readonly` DTO in the same `Command\u002F` directory.\n\nKeep a handler and its view coherent:\n\n- The view name mirrors the handler name. A `List\u003CX>Handler` returns a\n  `List\u003CX>View`, verb-first, for example `ListIssuesHandler` returns\n  `ListIssuesView`. Do not invert it to `\u003CX>ListView`.\n- The returned data contains what the handler name promises. A\n  `ShowProjectHandler` that returns a bare `list\u003CIssue>` is wrong, because the\n  name leads you to expect a `Project`. A `Show\u003CX>Handler` returns a view that\n  contains the looked-up `\u003CX>` and its related data. For example,\n  `ShowProjectHandler` returns `ProjectDetailView { public Project $project; … }`.\n  The controller then reads the entity off the view (`'project' => $view->project`),\n  and not from the route parameter separately.\n\nKeep the `Show*` family (noun-first, `ProjectDetailView`) and the `List*` family\n(verb-first, `ListIssuesView`) distinct. Match the family you extend. Do not\nunify them.\n\n## Enforced shapes (gamache PHPStan rules)\n\n`Gamache\\PHPStan\\CommandShapeRule` and `HandlerShapeRule` run under `just ci` on\nevery class in a `Command\\` namespace.\n\n- A command is a class whose name does not end in `Handler` and that has no\n  parent class. It must be `final readonly`, with no public method besides\n  `__construct()`. Identifiers: `command.notFinalReadonly`,\n  `command.hasPublicMethods`.\n- A handler is a class whose name ends in `Handler`. It must be `final readonly`,\n  with exactly one public method, `__invoke()`. Identifiers:\n  `handler.notFinalReadonly`, `handler.invalidShape`.\n- Symfony console commands extend `Symfony\\...\\Command`, so the rule skips them.\n  They live in `Command\u002FConsole\u002F`.\n\n## Calling from the controller\n\nInject the handler and invoke it as a callable. The controller only parses the\nrequest, calls the handler, handles `DomainErrors` and returns a response.\n\n```php\npublic function __construct(\n    private readonly CreateIssueHandler $createIssueHandler,\n) {\n}\n\n\u002F\u002F inside __invoke(), after $form->isValid():\n$issue = ($this->createIssueHandler)(new CreateIssueCommand(\n    project: $project,\n    title: $formRequest->title ?: throw new \\LogicException('title required after validation'),\n    description: $formRequest->description,\n));\n```\n\n## DomainErrors, the domain validation failure channel\n\n`App\\Exception\\DomainErrors` (`src\u002FException\u002FDomainErrors.php`) carries\nfield-level domain failures from the handler to the controller. Its payload is a\n`non-empty-array\u003Cstring, string>` of field name to translation key. Never throw\nit with an empty array.\n\nIn the handler, collect the failures and `throw new DomainErrors($errors)`. This\ncovers uniqueness and duplicate checks, and state preconditions such as\n\"resource already in desired state\". The handler injects the repositories it\nneeds and enforces the invariant itself. The controller must never pre-check a\ndomain rule before it calls the handler.\n\nIn the controller, catch the exception and map it onto the form. Inject\n`TranslatorInterface $translator`.\n\n```php\n} catch (DomainErrors $e) {\n    foreach ($e->errors as $field => $translationKey) {\n        $form->get($field)->addError(new FormError($this->translator->trans($translationKey)));\n    }\n}\n```\n\nThen re-render with `renderFormResponse()`, which sets HTTP 422 on a submitted\nform.\n\n## Auditing a domain event\n\nA handler records its domain event through `Ubermuda\\AuditBundle\\Auditor`. Inject\n`Auditor` and call `record()`. Do not log the same event beside the record,\nbecause the package's Monolog sink writes the log line for it. A second logger\nemits the event twice, and no assertion on the record can see that.\n\nA handler that also calls an external service, or runs a batch job, keeps its\nlogger for that call. Stripe, the async export and the site-review outbox drain\ndo this. The record answers what happened and to whom. The log line beside it\ncarries the diagnostics the trail must not hold.\n`DirectLogging::assertDiagnosticsLoggedBeside()` pins that split.\n\n```php\n$this->auditor->record(\n    'board.card_deleted',\n    AuditOutcome::Success,\n    ['cardId' => $cardId, 'projectId' => $projectId],\n    new AuditSubject('card', $cardId),\n);\n```\n\nThe operation name matches `\u002F^[a-z][a-z0-9_]*\\.[a-z][a-z0-9_]*$\u002F`. Write the\nmodule first, then one snake_case outcome phrase, and keep one namespace per\nmodule. gamache's `AuditOperationNameRule` enforces the pattern through PHPStan.\n\nRecord after the transaction commits, never inside the closure. The sink drains\nat `kernel.terminate`, so a record written inside outlives a rollback. Snapshot\nthe ids and the scalars before a delete, because the removed entity carries no\nid. Put in the context what answers a later question, such as the source status\nand the target status of a move. Keep user prose out, and record a count or a\nboolean instead. `RecordingAuditor` and `DirectLogging::assertRemovedFrom()` in\n`tests\u002FSupport\u002F` assert the record and the absent logger.\n\n## Handler composition\n\nA handler may inject another handler and call it as a callable,\n`($this->subHandler)(new SubCommand(...))`. Do this only when other call sites\nalso invoke the sub-operation. If it is only ever a sub-step, inline the logic.\n\nThe caller decides whether `DomainErrors` from the sub-handler propagates, or is\na tolerated fallback. Check the values, which are translation keys, with\n`in_array`. Re-throw anything unexpected.\n\n```php\ntry {\n    ($this->openBrainstorm)(new OpenBrainstormCommand($conversation));\n} catch (DomainErrors $e) {\n    if (!\\in_array('brainstorm.error.no_inference_key', $e->errors, true)) {\n        throw $e;\n    }\n    $this->logger->info('project.brainstorm_open_skipped', [...]);\n}\n```\n\n## Related conventions\n\nThe examples above are illustrative. The skeleton ships no concrete command\nclasses of its own. For the surrounding conventions (controllers, forms and\nDTOs, flash messages, logging), see `project-backend`. For handler tests, see\n`project-testing`.\n",{"name":5,"description":7},"main","b0ae29efd5410c4e5bf9a6ed6aed4b6c1d82e55a",".agents\u002Fskills\u002Fproject-command-handler",0,"https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe","https:\u002F\u002Floupe.ac\u002F","https:\u002F\u002Fgithub.com\u002Floupe-ac","The control plane for your agent loops.","2026-11-15 04:50:14",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add loupe-ac\u002Floupe --skill project-command-handler",{"tool":39,"command":40},"bunx","bunx skills add loupe-ac\u002Floupe --skill project-command-handler",{"tool":42,"command":43},"pnpm","pnpm dlx skills add loupe-ac\u002Floupe --skill project-command-handler","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-command-handler\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75XHSK6MYZ0BH7PJHP378QV","loupe-workers","Use when reading worker runs or bridges through the loupe MCP, stopping, resuming or holding workers, cancelling a bridge command, or recovering workers after a usage limit or network outage.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-workers\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75XHPW77P75PPWY8Z7Q9XMZ","loupe-site-review","Use when acting on live-review feedback through the loupe MCP: reading the feedback of a card or project, fixing it, or marking it addressed.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-site-review\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75XHK6EZP2FZRQ1B4PS4CGH","loupe-inbox","Use when an agent needs a decision, answer or review from the project owner through the loupe MCP, hands a question or to-do to a person, resumes after an ask closed, or needs its session id.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-inbox\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75XHDN9XG71R4T248BZ540A","loupe-documents","Use when writing or revising a document for the Loupe app through the loupe MCP, such as a plan, spec, RFC, audit report or retrospective.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-documents\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75XHBERM2SWJ7SJ1EB5M4SB","loupe-discovery","Use when a bridge runs a discovery run of a Loupe project, when a prompt names loupe-discovery, or when writing a readiness report.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-discovery\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75XH7X2KCFWPVMQJJAMPYJN","loupe-board","Use when working a Loupe project board through the loupe MCP: reading or writing a card, moving a card, changing the columns, or linking a document or a pull request to a card.","https:\u002F\u002Fgithub.com\u002Floupe-ac\u002Floupe\u002Fblob\u002Fmain\u002Fplugins\u002Floupe\u002Fskills\u002Floupe-board\u002FSKILL.md",[],[]]