miscsubjects : carte d'agent A2A
Cette page ne recopie aucun annuaire. Tout ce qu'elle affiche vient de la carte que cet agent publie lui-même, relue chaque jour.
Carte inutilisable en l'état
Un agent qui lit cette carte ne peut pas s'en servir.
Ce que la carte déclare
- Fournisseur
- miscsubjects.com
- Point d'entrée
- https://miscsubjects.com/api/dispatch
- Version du protocole
- 1.0
- Transport
- HTTP+JSON
- Forme de la carte
- antérieure à la v1.0
Depuis quand cet agent répond
- Suivi depuis
- 2026-09-08
- Dernière réponse
- 2026-09-08
- Relevés
- 1
- Réponses
- 1
Compétences déclarées
- coding-lawUse before the first edit of any file under functions/, scripts/, migrations/, workers/, apps-script/, .claude/skills/, .agents/skills/, schema.sql or wrangler.toml — and again immediately before every git commit. Take a…
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- executing-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work
- grill-meA relentless interview to sharpen a plan or design.
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind…
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
- webapp-testingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
- writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
- seo-distribution-lawUse when writing, reviewing, or shipping anything that affects how this site is found, indexed, shared, or syndicated — SEO heads, sitemaps, feeds, share surfaces, network posting, or the self-score. The site's…
- agent-work-lawUse at the start of every session operating miscsubjects.com, and whenever deciding what to work on, whether work is finished, or what to do about a failure. The infrastructure is the authority; this skill tells you…
- article-editingUse when creating, editing, sourcing, illustrating, exporting, or deleting any article on miscsubjects.com — from the admin studio, curl, a coding agent, a Cloudflare Gateway model, or Google Sheets. One REST contract…
- self-promotionThe build's standing procedure for promoting itself — deciding whether, whom, when, on which channel, and with which artifact to make contact whenever something ships or a reply lands. Governs the allocation, not the…
- shared-failure-to-skillUse when the owner reports a recurring failure, repeated fix, or systemic issue. Convert the failure into a skill and a mechanical gate so it stops repeating.
- shared-no-new-problemsUse when the owner asks for a fix or reports a failure. Fix it without asking permission and without creating new problems.
- shared-rule-captureUse when the owner restates a rule, correction, or constraint, or when a governor report shows high owner-restatement counts.
- shared-say-noUse ONLY when answering an evaluative question — "anything to add", "any ideas", "anything wrong", "is this good/A+", a review, an audit, or a decision about whether something can be deleted. NEVER use it to answer a…
- skill-creatorCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill…
- writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment
Constats
- ErreurChamp obligatoire absent : version
version - AvertissementCarte écrite dans la forme antérieure à la v1.0 du protocole
- Remarqueurl a été déplacé vers supportedInterfaces[0].url en v1.0
url - RemarqueprotocolVersion a été déplacé vers supportedInterfaces[].protocolVersion en v1.0
protocolVersion - RemarquepreferredTransport a été déplacé vers supportedInterfaces[0].protocolBinding en v1.0
preferredTransport - RemarqueadditionalInterfaces a été déplacé vers supportedInterfaces[] en v1.0
additionalInterfaces
Badge
Chercher un agent par capacité
Dernier relevé : 2026-09-08