notification
/notification
Pomaga przejść ze starego Notification API na tematy i zasoby subskrypcji oraz zdarzenia platformy handlowej, np. oferty i licytacje.
- Autor
- eBay ↗
- Repozytorium
- public-api-migration-skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 03.07.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 121
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.07.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Pomaga przejść ze starego Notification API na tematy i zasoby subskrypcji oraz zdarzenia platformy handlowej, np. oferty i licytacje.
Oryginalny opis (EN)
Migration guidance for traditional Notification API calls and traditional platform notification events to Notification API topics and subscription resources. Trigger when user mentions: GetNotificationPreferences, SetNotificationPreferences, GetNotificationsUsage, or platform events such as BestOffer, BidPlaced, FeedbackReceived, EndOfAuction, My Messages notifications, watch-list notifications, or asks how to migrate Trading platform notifications to Notification API topics. Covers 3 traditional Notification API calls, concrete mapped platform events with bundled evidence, and explicit unreso
Jak działa
- When To Apply
- Key Migration Patterns
- Answer Constraints
- Workflow Notes
- Evidence Boundaries
- Field-Level Details
Podgląd SKILL.md
--- name: notification description: | Migration guidance for traditional Notification API calls and traditional platform notification events to Notification API topics and subscription resources. Trigger when user mentions: GetNotificationPreferences, SetNotificationPreferences, GetNotificationsUsage, or platform events such as BestOffer, BidPlaced, FeedbackReceived, EndOfAuction, My Messages notifications, watch-list notifications, or asks how to migrate Trading platform notifications to Notification API topics. Covers 3 traditional Notification API calls, concrete mapped platform events with bundled evidence, and explicit unresolved-status inventory for remaining notification rows. Do NOT use for order retrieval, listing creation, or non-notification migration tasks. --- # Notification Migration Skill This skill covers traditional Notification API management and traditional platform notification event migration to the modern Notification API subscription and topic model. ## When To Apply Use this package when you need to: - migrate `GetNotificationPreferences`, `SetNotificationPreferences`, or `GetNotificationsUsage` - map a traditional platform notification event to a modern Notification API topic - interpret grouped migrations such as `OFFER_ACTIVITY`, `AUCTION_ACTIVITY`, `NEW_MESSAGE` or `LISTING` - confirm whether a traditional event is `No Replacement`, still pending, or only has guide-backed fallback guidance ## Key Migration Patterns - Traditional event enablement becomes topic subscriptions returned by `getSubscriptions`. - `SetNotificationPreferences` splits into destination, config, and subscription resource methods instead of one combined traditional call. - Several traditional events consolidate into one modern topic and require payload filters such as `OfferType`, `OfferStatus`, `AuctionActivity`, `WatchlistRevision`, or listing `reason`. - Some traditional rows remain unresolved or explicitly `No Replacement`; those statuses must be preserved exactly. ## Answer Constraints - Use the packaged files to find the answer, but do not mention package file names or internal paths such as `INDEX.md`, `INTENTS.md`, `operation-mapping.md`, or `references/operations/*` in the user-facing response. - Do not answer with only an internal reference or lookup instruction. Return the migration guidance directly. - When the prompt asks about multiple topics, answer each topic inline in the response instead of redirecting the user to an internal lookup file. - Unless the user explicitly asks for a brief summary, include at least one concrete migration example in the response when a bundled example exists for the mapped traditional call, event, or modern replacement. - Prefer examples that show the traditional concept and the modern replacement together, such as a traditional event mapping to a modern topic plus the payload field or filter value that makes the mapping actionable. - When answering operation-migration questions, include a short example of the modern request, response, or subscription shape instead of naming the replacement methods only. - When a modern topic has no bundled example, do not fall back to a purely abstract answer. Use the bundled traditional example plus the documented modern topic name and discriminator fields or values to show what changes during migration, and say explicitly if the exact modern payload shape is not bundled locally. ## Workflow Notes - Start with [INDEX.md](./INDEX.md) for the notification inventory. - Use [INTENTS.md](./INTENTS.md) when the task is phrased as a workflow rather than as one operation or event name. - Use [references/operation-mapping.md](./references/operation-mapping.md) for direct traditional-to-modern mappings and guide extracts. - Use [rules/notification-subscription-model.md](./rules/notification-subscription-model.md) before migrating destination, config, or subscription setup. - Use [rules/topic-consolidation-and-fallbacks.md](./rules/topic-consolidation-and-fallbacks.md) for grouped-topic migrations such as `OFFER_ACTIVITY`, `AUCTION_ACTIVITY`, `NEW_MESSAGE` and `LISTING`. - Use [rules/unresolved-event-statuses.md](./rules/unresolved-event-statuses.md) before answering `No Replacement`, pending, or conflicting-status questions. ## Evidence Boundaries - Guide-derived notification caveats and fallback notes are extracted into the relevant entries in `references/operation-mapping.md`. - Bundled traditional event and Notification API pages are included only for the concrete mapped rows covered in `references/operation-mapping.md`. - Local standalone modern topic docs are still missing for `LISTING`; this package keeps those gaps explicit instead of inventing details. ## Field-Level Details Field-level request and response mapping is limited to what is explicitly present in the bundled guide and doc files in this package. If a local source gap is called out in `references/operations/`, keep that gap explicit.
Pliki w paczce (121)
- INDEX.md 6 KB
- INTENTS.md 5 KB
- SKILL.md 5 KB
- references/operation-mapping.md 34 KB
- references/operations/AUCTION_ACTIVITY_doc.md 6 KB
- references/operations/AUCTION_ENDED_doc.md 5 KB
- references/operations/AUTHORIZATION_REVOCATION_doc.md 5 KB
- references/operations/AskSellerQuestion_doc.md 1 KB
- references/operations/AskSellerQuestion_example.md 1 KB
- references/operations/AuctionCheckoutComplete_doc.md 2 KB
- references/operations/AuctionCheckoutComplete_example.md 5 KB
- references/operations/BUYER_QUESTION_doc.md 5 KB
- references/operations/BUYER_REQUESTED_PURCHASE_QUOTE_doc.md 5 KB
- references/operations/BestOfferDeclined_doc.md 1 KB
- references/operations/BestOfferDeclined_example.md 1 KB
- references/operations/BestOfferPlaced_doc.md 1 KB
- references/operations/BestOfferPlaced_example.md 1 KB
- references/operations/BestOffer_doc.md 1 KB
- references/operations/BestOffer_example.md 1 KB
- references/operations/BidItemEndingSoon_doc.md 1 KB
- references/operations/BidItemEndingSoon_example.md 1 KB
- references/operations/BidPlaced_doc.md 1 KB
- references/operations/BidPlaced_example.md 4 KB
- references/operations/BidReceived_doc.md 9 KB
- references/operations/BidReceived_example.md 7 KB
- references/operations/CheckoutBuyerRequestsTotal_doc.md 1 KB
- references/operations/CheckoutBuyerRequestsTotal_example.md 3 KB
- references/operations/CounterOfferReceived_doc.md 1 KB
- references/operations/CounterOfferReceived_example.md 1 KB
- references/operations/EndOfAuction_doc.md 1 KB
- references/operations/EndOfAuction_example.md 6 KB
- references/operations/FEEDBACK_LEFT_doc.md 13 KB
- references/operations/FEEDBACK_RECEIVED_doc.md 13 KB
- references/operations/FEEDBACK_STAR_RATING_doc.md 6 KB
- references/operations/FeedbackLeft_doc.md 1 KB
- references/operations/FeedbackLeft_example.md 1 KB
- references/operations/FeedbackReceived_doc.md 1 KB
- references/operations/FeedbackReceived_example.md 1 KB
- references/operations/FeedbackStarChanged_doc.md 1 KB
- references/operations/FeedbackStarChanged_example.md 2 KB
- references/operations/Feedback_doc.md 1 KB
- references/operations/Feedback_example.md 1 KB
- references/operations/FixedPriceTransaction_doc.md 1 KB
- references/operations/FixedPriceTransaction_example.md 4 KB
- references/operations/GetNotificationPreferences_doc.md 5 KB
- references/operations/GetNotificationPreferences_example.md 8 KB
- references/operations/GetNotificationsUsage_doc.md 1 KB
- references/operations/GetNotificationsUsage_example.md 3 KB
- references/operations/ITEM_MARKED_SHIPPED_doc.md 5 KB
- references/operations/ItemAddedToWatchList_doc.md 1 KB
- references/operations/ItemAddedToWatchList_example.md 4 KB
- references/operations/ItemClosed_doc.md 1 KB
- references/operations/ItemClosed_example.md 5 KB
- references/operations/ItemListed_doc.md 1 KB
- references/operations/ItemListed_example.md 6 KB
- references/operations/ItemMarkedShipped_doc.md 1 KB
- references/operations/ItemMarkedShipped_example.md 1 KB
- references/operations/ItemReadyForPickup_doc.md 1 KB
- references/operations/ItemReadyForPickup_example.md 1 KB
- references/operations/ItemRemovedFromWatchList_doc.md 1 KB
- references/operations/ItemRemovedFromWatchList_example.md 4 KB
- references/operations/ItemRevisedAddCharity_doc.md 1 KB
- references/operations/ItemRevisedAddCharity_example.md 1 KB
- references/operations/ItemRevised_doc.md 1 KB
- references/operations/ItemRevised_example.md 3 KB
- references/operations/ItemSold_doc.md 1 KB
- references/operations/ItemSold_example.md 3 KB
- references/operations/ItemWon_doc.md 1 KB
- references/operations/ItemWon_example.md 4 KB
- references/operations/LISTING_doc.md 3 KB
- references/operations/M2MMessageStatusChange_doc.md 1 KB
- references/operations/M2MMessageStatusChange_example.md 1 KB
- references/operations/MyMessagesHighPriorityMessageHeader_doc.md 1 KB
- references/operations/MyMessagesHighPriorityMessage_doc.md 1 KB
- references/operations/MyMessagesHighPriorityMessage_example.md 2 KB
- references/operations/MyMessagesM2MMessageHeader_doc.md 1 KB
- references/operations/MyMessagesM2MMessageHeader_example.md 2 KB
- references/operations/MyMessagesM2MMessage_doc.md 3 KB
- references/operations/MyMessagesM2MMessage_example.md 2 KB
- references/operations/MyMessageseBayMessageHeader_doc.md 1 KB
- references/operations/MyMessageseBayMessageHeader_example.md 1 KB
- references/operations/MyMessageseBayMessage_doc.md 3 KB
- references/operations/MyMessageseBayMessage_example.md 2 KB
- references/operations/NEW_MESSAGE_doc.md 6 KB
- references/operations/OFFER_ACTIVITY_doc.md 6 KB
- references/operations/ORDER_CONFIRMATION_doc.md 5 KB
- references/operations/OutBid_doc.md 1 KB
- references/operations/OutBid_example.md 4 KB
- references/operations/SecondChanceOffer_doc.md 1 KB
- references/operations/SecondChanceOffer_example.md 2 KB
- references/operations/SetNotificationPreferences_doc.md 6 KB
- references/operations/SetNotificationPreferences_example.md 2 KB
- references/operations/ShoppingCartItemEndingSoon_doc.md 1 KB
- references/operations/ShoppingCartItemEndingSoon_example.md 1 KB
- references/operations/TokenRevocation_doc.md 1 KB
- references/operations/TokenRevocation_example.md 1 KB
- references/operations/WatchedItemEndingSoon_doc.md 1 KB
- references/operations/WatchedItemEndingSoon_example.md 1 KB
- references/operations/createDestination_doc.md 1 KB
- references/operations/createDestination_example.md 1 KB
- references/operations/createSubscription_doc.md 1 KB
- references/operations/createSubscription_example.md 1 KB
- references/operations/deleteSubscription_doc.md 1 KB
- references/operations/deleteSubscription_example.md 1 KB
- references/operations/disableSubscription_doc.md 1 KB
- references/operations/disableSubscription_example.md 1 KB
- references/operations/enableSubscription_doc.md 1 KB
- references/operations/enableSubscription_example.md 1 KB
- references/operations/getConfig_doc.md 1 KB
- references/operations/getConfig_example.md 1 KB
- references/operations/getSubscriptions_doc.md 1 KB
- references/operations/getSubscriptions_example.md 1 KB
- references/operations/updateConfig_doc.md 1 KB
- references/operations/updateConfig_example.md 1 KB
- references/operations/updateDestination_doc.md 1 KB
- references/operations/updateDestination_example.md 1 KB
- references/operations/updateSubscription_doc.md 1 KB
- references/operations/updateSubscription_example.md 1 KB
- rules/notification-subscription-model.md 1 KB
- rules/topic-consolidation-and-fallbacks.md 2 KB
- rules/unresolved-event-statuses.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · eBay/public-api-migration-skills | 100 | Apache-2.0 |
| metabase/metabase-cli | 100 | AGPL-3.0 |
| virtualian/pai | 95 | MIT |
| mikeyobrien/rho | 95 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki cd3bc0ecda80 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100notification-platform
Prowadzi przez dodawanie powiadomień, własnych rendererów i nowych providerów w NotificationPlatform Sentry. - 100orchardcore-notifications
Zarządza powiadomieniami w Orchard Core: wiadomościami, dostarczaniem przez e-mail i SMS, zdarzeniami oraz akcjami workflow. - 100notification-system
Projektuje i wdraża wielokanałowe systemy powiadomień z dostarczaniem e-mail, push i w aplikacji: preferencje użytkownika, potoki dostarczania, ponowienia i routing między kanałami. - 100communication
Przeprowadza migrację z dawnych wywołań wiadomości i opinii do Feedback API oraz Message API opartych na konwersacjach. - 90mobile-push-notifications
Pomaga wdrożyć powiadomienia push na iOS, Androidzie, Flutterze i React Native: uprawnienia, tokeny, payloady i kanały. - 100maui-push-notifications
Prowadzi przez dodanie powiadomień push do aplikacji .NET MAUI: Firebase Cloud Messaging, Apple Push Notification Service, Azure Notification Hubs, backend ASP.NET Core i klient MAUI.