vendor-status
Check vendor portal credentials and cookie expiration status. Use when checking vendor status, credentials, or cookie expiration.
When & Why to Use This Skill
This Claude skill provides a specialized monitoring solution for vendor portal credentials and cookie expiration statuses. It is designed to ensure the continuity of automated workflows by proactively tracking session validity, managing authentication secrets, and providing structured recovery procedures for common authentication hurdles like CAPTCHAs and MFA.
Use Cases
- Proactive Session Monitoring: Automatically track the expiration dates of session cookies for various vendor portals (e.g., Google Ads, IBJ) to prevent unexpected automation downtime.
- Credential Recovery Workflow: Streamline the process of manual re-authentication and updating Google Cloud Secret Manager with fresh session data when automated logins fail.
- Authentication Troubleshooting: Quickly identify the root cause of access issues, distinguishing between simple session timeouts, bot detection triggers, or required multi-factor authentication.
- Automated Status Reporting: Generate quick summaries of credential health and upcoming expiration warnings directly within the development environment or via notification systems.
| name | vendor-status |
|---|---|
| description | Check vendor portal credentials and cookie expiration status. Use when checking vendor status, credentials, or cookie expiration. |
| allowed-tools | Bash, Read, Grep |
Vendor Credential Status
Monitors vendor portal authentication status and cookie expiration for Phase 3 vendor automation.
Quick Status Check
Run in Apps Script editor:
checkVendorCookieStatus();
Returns:
- Cookie validity status
- Days until expiration
- Warning status
Vendor Schedule Reference
| Vendor | Day | Key | Portal URL |
|---|---|---|---|
| Aitemasu | 1st | aitemasu |
https://app.aitemasu.me/ |
| Google Ads | 4th | google-ads |
https://ads.google.com/ |
| IBJ | 11th | ibj |
https://www.ibjapan.com/ |
Configuration Location
Vendor configs are in src/config.ts:
VENDOR_CONFIGS.aitemasuVENDOR_CONFIGS.ibjVENDOR_CONFIGS.googleAds
Credential Recovery Workflow
When auth failure notification is received:
Open vendor portal in browser
Log in manually and complete verification (CAPTCHA, MFA)
Export cookies using Cookie-Editor extension (JSON format)
Update Secret Manager:
gcloud secrets versions add VENDOR_COOKIES_{VENDOR_KEY} --data-file=cookies.jsonRecord update in Apps Script:
updateVendorCookieMetadata('vendor-key', 30); // 30 days expiration
Common Auth Failure Types
| Type | Cause | Recovery |
|---|---|---|
session_expired |
Login timed out | Re-login, export cookies |
captcha_required |
Bot detection | Complete CAPTCHA, export |
mfa_required |
2FA needed | Complete MFA, export |
cookie_expired |
Cookie past expiry | Re-login, export cookies |
Manual Processing
Process a specific vendor outside schedule:
processVendorManually('aitemasu');
processVendorManually('google-ads');
processVendorManually('ibj');
Test Notifications
Verify notification system works:
testAuthFailureNotification('aitemasu');
Monitoring Commands Summary
| Command | Purpose |
|---|---|
checkVendorCookieStatus() |
View all vendor cookie status |
showVendorSchedule() |
View processing schedule |
updateVendorCookieMetadata(key, days) |
Record cookie refresh |
processVendorManually(key) |
Force process vendor |
testAuthFailureNotification(key) |
Test notification email |