feat(skills): Add 8 operational domain skills (logistics, manufacturing, retail, energy)#290
Merged
affaan-m merged 6 commits intoaffaan-m:mainfrom Mar 11, 2026
Merged
Conversation
Adds skills covering logistics, manufacturing, retail, and energy operations. Each codifies 15+ years of real industry expertise. Skills: logistics-exception-management, carrier-relationship-management, customs-trade-compliance, inventory-demand-planning, returns-reverse-logistics, production-scheduling, quality-nonconformance, energy-procurement Source: https://github.com/ai-evos/agent-skills License: Apache-2.0 Co-authored-by: Cursor <[email protected]>
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughAdds eight new domain skill documentation files covering carrier relationship management, customs trade compliance, energy procurement, inventory demand planning, logistics exception management, production scheduling, quality nonconformance, and returns/reverse logistics. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
skills/production-scheduling/SKILL.md (1)
5-10: Inconsistent spelling:optimisationvsoptimizationused within the same document.The frontmatter description (Line 5), section heading "Changeover Optimisation" (Line 40), and Additional Resources (Line 213) use the British spelling, while body prose on Lines 48 and 124 uses the American spelling. Pick one variant and apply it consistently throughout.
✏️ Proposed fix (American spelling throughout, to match body prose)
- changeover optimisation, and bottleneck resolution in discrete and batch + changeover optimization, and bottleneck resolution in discrete and batch-### Changeover Optimisation +### Changeover Optimization- Due date compliance trumps changeover optimisation. + Due date compliance trumps changeover optimization.-- For detailed decision frameworks, scheduling algorithms, and optimisation methodologies, see +- For detailed decision frameworks, scheduling algorithms, and optimization methodologies, seeAlso applies to: 40-48, 124-124, 213-213
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/production-scheduling/SKILL.md` around lines 5 - 10, The document uses both British ("optimisation") and American ("optimization") spellings; choose one variant (recommend American to match body prose) and perform a global replace in SKILL.md so all occurrences are consistent—update the frontmatter description, the "Changeover Optimisation" heading, body instances (e.g., the paragraph that references changeovers around the Changeover section) and the Additional Resources entry; ensure you also update any related compound phrases (e.g., "changeover optimisation" => "changeover optimization") and verify headings and TOC entries match exactly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 215-217: The skill docs reference three missing files
(decision-frameworks.md, edge-cases.md, communication-templates.md) via relative
links in SKILL.md and seven other skill files; fix by either adding those three
reference files to this PR under the referenced references/ path or by updating
each reference link in the SKILL.md (and the other 7 skill files) to a valid
absolute URL where the documents live; ensure you update all occurrences of
decision-frameworks.md, edge-cases.md, and communication-templates.md so no
cross-reference remains broken and add a note in the PR description if you
choose to defer adding the files to a follow-up PR.
- Around line 1-18: The file SKILL.md for the returns-reverse-logistics skill
violates the lowercase-with-hyphens naming rule; rename SKILL.md to a lowercase
hyphenated name (for example returns-reverse-logistics-skill.md or skill.md) and
update any references to it (e.g., in manifests or imports that use the
filename), ensuring the metadata.name "returns-reverse-logistics" remains
unchanged; apply the same rename pattern to the other seven SKILL.md files so
all eight follow the lowercase-with-hyphens convention.
- Around line 20-217: The file is missing the mandated top-level Markdown
sections "When to Use", "How It Works", and "Examples"; insert three clearly
headed sections into SKILL.md (and the other seven skill files) after the
existing "Role and Context" or before "Core Knowledge" so the document structure
matches the skills guideline; under "When to Use" state the scenarios/triggers
for applying this skill (e.g., returns exceeding threshold, international
returns, recalled items), under "How It Works" outline the step-by-step workflow
and decision points (reference existing subsections like "Returns Policy Logic",
"Inspection and Grading", "Disposition Decision Trees", "Fraud Scoring Model"),
and under "Examples" add 3–5 concrete, short examples or YAML-like use cases
(e.g., Grade A electronics restock flow, hazmat return refusal, influencer bulk
return) to illustrate application.
- Line 13: The SKILL.md files list a broken homepage URL; update the homepage
frontmatter in each of the eight skill files
(skills/returns-reverse-logistics/SKILL.md,
skills/quality-nonconformance/SKILL.md,
skills/logistics-exception-management/SKILL.md,
skills/production-scheduling/SKILL.md,
skills/inventory-demand-planning/SKILL.md, skills/energy-procurement/SKILL.md,
skills/customs-trade-compliance/SKILL.md,
skills/carrier-relationship-management/SKILL.md) by replacing the invalid URL
"https://github.com/evos-ai/evos-capabilities" with the correct repository URL
"https://github.com/ai-evos/agent-skills" in the homepage frontmatter entry.
---
Nitpick comments:
In `@skills/production-scheduling/SKILL.md`:
- Around line 5-10: The document uses both British ("optimisation") and American
("optimization") spellings; choose one variant (recommend American to match body
prose) and perform a global replace in SKILL.md so all occurrences are
consistent—update the frontmatter description, the "Changeover Optimisation"
heading, body instances (e.g., the paragraph that references changeovers around
the Changeover section) and the Additional Resources entry; ensure you also
update any related compound phrases (e.g., "changeover optimisation" =>
"changeover optimization") and verify headings and TOC entries match exactly.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
skills/carrier-relationship-management/SKILL.mdskills/customs-trade-compliance/SKILL.mdskills/energy-procurement/SKILL.mdskills/inventory-demand-planning/SKILL.mdskills/logistics-exception-management/SKILL.mdskills/production-scheduling/SKILL.mdskills/quality-nonconformance/SKILL.mdskills/returns-reverse-logistics/SKILL.md
Comment on lines
+1
to
+18
| --- | ||
| name: returns-reverse-logistics | ||
| description: > | ||
| Codified expertise for returns authorisation, receipt and inspection, | ||
| disposition decisions, refund processing, fraud detection, and warranty | ||
| claims management. Informed by returns operations managers with 15+ years | ||
| experience. Includes grading frameworks, disposition economics, fraud | ||
| pattern recognition, and vendor recovery processes. Use when handling | ||
| product returns, reverse logistics, refund decisions, return fraud | ||
| detection, or warranty claims. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/evos-ai/evos-capabilities | ||
| metadata: | ||
| author: evos | ||
| clawdbot: | ||
| emoji: "🔄" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
SKILL.md filename violates the lowercase-with-hyphens naming convention (applies to all 8 files).
The coding guidelines require lowercase filenames (e.g., python-reviewer.md). All eight new files are named SKILL.md (uppercase). Rename to skill.md or a more descriptive lowercase name such as returns-reverse-logistics-skill.md.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` around lines 1 - 18, The file
SKILL.md for the returns-reverse-logistics skill violates the
lowercase-with-hyphens naming rule; rename SKILL.md to a lowercase hyphenated
name (for example returns-reverse-logistics-skill.md or skill.md) and update any
references to it (e.g., in manifests or imports that use the filename), ensuring
the metadata.name "returns-reverse-logistics" remains unchanged; apply the same
rename pattern to the other seven SKILL.md files so all eight follow the
lowercase-with-hyphens convention.
| detection, or warranty claims. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/evos-ai/evos-capabilities |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Find all files containing the homepage URL
rg 'homepage:.*evos' --type md --type jsonRepository: affaan-m/everything-claude-code
Length of output: 846
🌐 Web query:
GitHub repository evos-ai/evos-capabilities exists
💡 Result:
The GitHub repository evos-ai/evos-capabilities is not publicly accessible / does not exist at that URL: requesting https://github.com/evos-ai/evos-capabilities returns 404 Not Found. [1]
🌐 Web query:
GitHub repository ai-evos/agent-skills exists
💡 Result:
Yes — the GitHub repository ai-evos/agent-skills exists and is public. [1]
Update homepage URL across all 8 skill files — currently points to non-existent repository.
The homepage URL https://github.com/evos-ai/evos-capabilities does not exist (404 Not Found). The correct repository is https://github.com/ai-evos/agent-skills. Update all 8 skill files: skills/returns-reverse-logistics/SKILL.md, skills/quality-nonconformance/SKILL.md, skills/logistics-exception-management/SKILL.md, skills/production-scheduling/SKILL.md, skills/inventory-demand-planning/SKILL.md, skills/energy-procurement/SKILL.md, skills/customs-trade-compliance/SKILL.md, and skills/carrier-relationship-management/SKILL.md.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` at line 13, The SKILL.md files
list a broken homepage URL; update the homepage frontmatter in each of the eight
skill files (skills/returns-reverse-logistics/SKILL.md,
skills/quality-nonconformance/SKILL.md,
skills/logistics-exception-management/SKILL.md,
skills/production-scheduling/SKILL.md,
skills/inventory-demand-planning/SKILL.md, skills/energy-procurement/SKILL.md,
skills/customs-trade-compliance/SKILL.md,
skills/carrier-relationship-management/SKILL.md) by replacing the invalid URL
"https://github.com/evos-ai/evos-capabilities" with the correct repository URL
"https://github.com/ai-evos/agent-skills" in the homepage frontmatter entry.
Comment on lines
+20
to
+217
| # Returns & Reverse Logistics | ||
|
|
||
| ## Role and Context | ||
|
|
||
| You are a senior returns operations manager with 15+ years handling the full returns lifecycle across retail, e-commerce, and omnichannel environments. Your responsibilities span return merchandise authorisation (RMA), receiving and inspection, condition grading, disposition routing, refund and credit processing, fraud detection, vendor recovery (RTV), and warranty claims management. Your systems include OMS (order management), WMS (warehouse management), RMS (returns management), CRM, fraud detection platforms, and vendor portals. You balance customer satisfaction against margin protection, processing speed against inspection accuracy, and fraud prevention against false-positive customer friction. | ||
|
|
||
| ## Core Knowledge | ||
|
|
||
| ### Returns Policy Logic | ||
|
|
||
| Every return starts with policy evaluation. The policy engine must account for overlapping and sometimes conflicting rules: | ||
|
|
||
| - **Standard return window:** Typically 30 days from delivery for most general merchandise. Electronics often 15 days. Perishables non-returnable. Furniture/mattresses 30-90 days with specific condition requirements. Extended holiday windows (purchases Nov 1 – Dec 31 returnable through Jan 31) create a surge that peaks mid-January. | ||
| - **Condition requirements:** Most policies require original packaging, all accessories, and no signs of use beyond reasonable inspection. "Reasonable inspection" is where disputes live — a customer who removed laptop screen protector film has technically altered the product but this is normal unboxing behaviour. | ||
| - **Receipt and proof of purchase:** POS transaction lookup by credit card, loyalty number, or phone number has largely replaced paper receipts. Gift receipts entitle the bearer to exchange or store credit at the purchase price, never cash refund. No-receipt returns are capped (typically $50-75 per transaction, 3 per rolling 12 months) and refunded at lowest recent selling price. | ||
| - **Restocking fees:** Applied to opened electronics (15%), special-order items (20-25%), and large/bulky items requiring return shipping coordination. Waived for defective products or fulfilment errors. The decision to waive for customer goodwill requires margin awareness — waiving a $45 restocking fee on a $300 item with 28% margin costs more than it appears. | ||
| - **Cross-channel returns:** Buy-online-return-in-store (BORIS) is expected by customers and operationally complex. Online prices may differ from store prices. The refund should match the original purchase price, not the current store shelf price. Inventory system must accept the unit back into store inventory or flag for return-to-DC. | ||
| - **International returns:** Duty drawback eligibility requires proof of re-export within the statutory window (typically 3-5 years depending on country). Return shipping costs often exceed product value for low-cost items — offer "returnless refund" when shipping exceeds 40% of product value. Customs declarations for returned goods differ from original export documentation. | ||
| - **Exceptions:** Price-match returns (customer found it cheaper), buyer's remorse beyond window with compelling circumstances, defective products outside warranty, and loyalty tier overrides (top-tier customers get extended windows and waived fees) all require judgment frameworks rather than rigid rules. | ||
|
|
||
| ### Inspection and Grading | ||
|
|
||
| Returned products require consistent grading that drives disposition decisions. Speed and accuracy are in tension — a 30-second visual inspection moves volume but misses cosmetic defects; a 5-minute functional test catches everything but creates bottleneck at scale: | ||
|
|
||
| - **Grade A (Like New):** Original packaging intact, all accessories present, no signs of use, passes functional test. Restockable as new or "open box" with full margin recovery (85-100% of original retail). Target inspection time: 45-90 seconds. | ||
| - **Grade B (Good):** Minor cosmetic wear, original packaging may be damaged or missing outer sleeve, all accessories present, fully functional. Restockable as "open box" or "renewed" at 60-80% of retail. May need repackaging ($2-5 per unit). Target inspection time: 90-180 seconds. | ||
| - **Grade C (Fair):** Visible wear, scratches, or minor damage. Missing accessories that cost <10% of unit value. Functional but cosmetically impaired. Sells through secondary channels (outlet, marketplace, liquidation) at 30-50% of retail. Refurbishment possible if cost < 20% of recovered value. | ||
| - **Grade D (Salvage/Parts):** Non-functional, heavily damaged, or missing critical components. Salvageable for parts or materials recovery at 5-15% of retail. If parts recovery isn't viable, route to recycling or destruction. | ||
|
|
||
| Grading standards vary by category. Consumer electronics require functional testing (power on, screen check, connectivity) adding 2-4 minutes per unit. Apparel inspection focuses on stains, odour, stretched fabric, and missing tags — experienced inspectors use the "arm's length sniff test" and UV light for stain detection. Cosmetics and personal care items are almost never restockable once opened due to health regulations. | ||
|
|
||
| ### Disposition Decision Trees | ||
|
|
||
| Disposition is where returns either recover value or destroy margin. The routing decision is economics-driven: | ||
|
|
||
| - **Restock as new:** Only Grade A with complete packaging. Product must pass any required functional/safety testing. Relabelling or resealing may trigger regulatory issues (FTC "used as new" enforcement). Best for high-margin items where the restocking cost ($3-8 per unit) is trivial relative to recovered value. | ||
| - **Repackage and sell as "open box":** Grade A with damaged packaging or Grade B items. Repackaging cost ($5-15 depending on complexity) must be justified by the margin difference between open-box and next-lower channel. Electronics and small appliances are the sweet spot. | ||
| - **Refurbish:** Economically viable when refurbishment cost < 40% of the refurbished selling price, and a refurbished sales channel exists (certified refurbished program, manufacturer's outlet). Common for premium electronics, power tools, and small appliances. Requires dedicated refurb station, spare parts inventory, and re-testing capacity. | ||
| - **Liquidate:** Grade C and some Grade B items where repackaging/refurb isn't justified. Liquidation channels include pallet auctions (B-Stock, DirectLiquidation, Bulq), wholesale liquidators (per-pound pricing for apparel, per-unit for electronics), and regional liquidators. Recovery rates: 5-20% of retail. Critical insight: mixing categories in a pallet destroys value — electronics/apparel/home goods pallets sell at the lowest-category rate. | ||
| - **Donate:** Tax-deductible at fair market value (FMV). More valuable than liquidation when FMV > liquidation recovery AND the company has sufficient tax liability to utilise the deduction. Brand protection: restrict donations of branded products that could end up in discount channels undermining brand positioning. | ||
| - **Destroy:** Required for recalled products, counterfeit items found in the return stream, products with regulatory disposal requirements (batteries, electronics with WEEE compliance, hazmat), and branded goods where any secondary market presence is unacceptable. Certificate of destruction required for compliance and tax documentation. | ||
|
|
||
| ### Fraud Detection | ||
|
|
||
| Return fraud costs US retailers $24B+ annually. The challenge is detection without creating friction for legitimate customers: | ||
|
|
||
| - **Wardrobing (wear and return):** Customer buys apparel or accessories, wears them for an event, returns them. Indicators: returns clustered around holidays/events, deodorant residue, makeup on collars, creased/stretched fabric inconsistent with "tried on." Countermeasure: black-light inspection for cosmetic traces, RFID security tags that customers aren't instructed to remove (if the tag is missing, the item was worn). | ||
| - **Receipt fraud:** Using found, stolen, or fabricated receipts to return shoplifted merchandise for cash. Declining as digital receipt lookup replaces paper, but still occurs. Countermeasure: require ID for all cash refunds, match return to original payment method, limit no-receipt returns per ID. | ||
| - **Swap fraud (return switching):** Returning a counterfeit, cheaper, or broken item in the packaging of a purchased item. Common in electronics (returning a used phone in a new phone box) and cosmetics (refilling a container with a cheaper product). Countermeasure: serial number verification at return, weight check against expected product weight, detailed inspection of high-value items before processing refund. | ||
| - **Serial returners:** Customers with return rates > 30% of purchases or > $5,000 in annual returns. Not all are fraudulent — some are genuinely indecisive or bracket-shopping (buying multiple sizes to try). Segment by: return reason consistency, product condition at return, net lifetime value after returns. A customer with $50K in purchases and $18K in returns (36% rate) but $32K net revenue is worth more than a customer with $15K in purchases and zero returns. | ||
| - **Bracketing:** Intentionally ordering multiple sizes/colours with the plan to return most. Legitimate shopping behaviour that becomes costly at scale. Address through fit technology (size recommendation tools, AR try-on), generous exchange policies (free exchange, restocking fee on return), and education rather than punishment. | ||
| - **Price arbitrage:** Purchasing during promotions/discounts, then returning at a different location or time for full-price credit. Policy must tie refund to actual purchase price regardless of current selling price. Cross-channel returns are the primary vector. | ||
| - **Organised retail crime (ORC):** Coordinated theft-and-return operations across multiple stores/identities. Indicators: high-value returns from multiple IDs at the same address, returns of commonly shoplifted categories (electronics, cosmetics, health), geographic clustering. Report to LP (loss prevention) team — this is beyond standard returns operations. | ||
|
|
||
| ### Vendor Recovery | ||
|
|
||
| Not all returns are the customer's fault. Defective products, fulfilment errors, and quality issues have a cost recovery path back to the vendor: | ||
|
|
||
| - **Return-to-vendor (RTV):** Defective products returned within the vendor's warranty or defect claim window. Process: accumulate defective units (minimum RTV shipment thresholds vary by vendor, typically $200-500), obtain RTV authorisation number, ship to vendor's designated return facility, track credit issuance. Common failure: letting RTV-eligible product sit in the returns warehouse past the vendor's claim window (often 90 days from receipt). | ||
| - **Defect claims:** When defect rate exceeds the vendor agreement threshold (typically 2-5%), file a formal defect claim for the excess. Requires defect documentation (photos, inspection notes, customer complaint data aggregated by SKU). Vendors will challenge — your data quality determines your recovery. | ||
| - **Vendor chargebacks:** For vendor-caused issues (wrong item shipped from vendor DC, mislabelled products, packaging failures) charge back the full cost including return shipping and processing labour. Requires a vendor compliance program with published standards and penalty schedules. | ||
| - **Credit vs replacement vs write-off:** If the vendor is solvent and responsive, pursue credit. If the vendor is overseas with difficult collections, negotiate replacement product. If the claim is small (< $200) and the vendor is a critical supplier, consider writing it off and noting it in the next contract negotiation. | ||
|
|
||
| ### Warranty Management | ||
|
|
||
| Warranty claims are distinct from returns and follow a different workflow: | ||
|
|
||
| - **Warranty vs return:** A return is a customer exercising their right to reverse a purchase (typically within 30 days, any reason). A warranty claim is a customer reporting a product defect within the warranty coverage period (90 days to lifetime). Different systems, different policies, different financial treatment. | ||
| - **Manufacturer vs retailer obligation:** The retailer is typically responsible for the return window. The manufacturer is responsible for the warranty period. Grey area: the "lemon" product that keeps failing within warranty — the customer wants a refund, the manufacturer offers repair, and the retailer is caught in the middle. | ||
| - **Extended warranties/protection plans:** Sold at point of sale with 30-60% margins. Claims against extended warranties are handled by the warranty provider (often a third party). Retailer's role is facilitating the claim, not processing it. Common complaint: customers don't distinguish between retailer return policy, manufacturer warranty, and extended warranty coverage. | ||
|
|
||
| ## Decision Frameworks | ||
|
|
||
| ### Disposition Routing by Category and Condition | ||
|
|
||
| | Category | Grade A | Grade B | Grade C | Grade D | | ||
| |---|---|---|---|---| | ||
| | Consumer Electronics | Restock (test first) | Open box / Renewed | Refurb if ROI > 40%, else liquidate | Parts harvest or e-waste | | ||
| | Apparel | Restock if tags on | Repackage / outlet | Liquidate by weight | Textile recycling | | ||
| | Home & Furniture | Restock | Open box with discount | Liquidate (local, avoid shipping) | Donate or destroy | | ||
| | Health & Beauty | Restock if sealed | Destroy (regulation) | Destroy | Destroy | | ||
| | Books & Media | Restock | Restock (discount) | Liquidate | Recycle | | ||
| | Sporting Goods | Restock | Open box | Refurb if cost < 25% value | Parts or donate | | ||
| | Toys & Games | Restock if sealed | Open box | Liquidate | Donate (if safety-compliant) | | ||
|
|
||
| ### Fraud Scoring Model | ||
|
|
||
| Score each return 0-100. Flag for review at 65+, hold refund at 80+: | ||
|
|
||
| | Signal | Points | Notes | | ||
| |---|---|---| | ||
| | Return rate > 30% (rolling 12 mo) | +15 | Adjusted for category norms | | ||
| | Item returned within 48 hours of delivery | +5 | Could be legitimate bracket shopping | | ||
| | High-value electronics, serial number mismatch | +40 | Near-certain swap fraud | | ||
| | Return reason changed between initiation and receipt | +10 | Inconsistency flag | | ||
| | Multiple returns same week | +10 | Cumulative with rate signal | | ||
| | Return from address different than shipping address | +10 | Gift returns excluded | | ||
| | Product weight differs > 5% from expected | +25 | Swap or missing components | | ||
| | Customer account < 30 days old | +10 | New account risk | | ||
| | No-receipt return | +15 | Higher risk of receipt fraud | | ||
| | Item in category with high shrink rate | +5 | Electronics, cosmetics, designer apparel | | ||
|
|
||
| ### Vendor Recovery ROI | ||
|
|
||
| Pursue vendor recovery when: `(Expected credit × probability of collection) > (Labour cost + shipping cost + relationship cost)`. Rules of thumb: | ||
|
|
||
| - Claims > $500: Always pursue. The math works even at 50% collection probability. | ||
| - Claims $200-500: Pursue if the vendor has a functional RTV programme and you can batch shipments. | ||
| - Claims < $200: Batch until threshold is met, or offset against next PO. Do not ship individual units. | ||
| - Overseas vendors: Increase minimum threshold to $1,000. Add 30% to expected processing time. | ||
|
|
||
| ### Return Policy Exception Logic | ||
|
|
||
| When a return falls outside standard policy, evaluate in this order: | ||
|
|
||
| 1. **Is the product defective?** If yes, accept regardless of window or condition. Defective products are the company's problem, not the customer's. | ||
| 2. **Is this a high-value customer?** (Top 10% by LTV) If yes, accept with standard refund. The retention math almost always favours the exception. | ||
| 3. **Is the request reasonable to a neutral observer?** A customer returning a winter coat in March that they bought in November (4 months, outside 30-day window) is understandable. A customer returning a swimsuit in December that they bought in June is less so. | ||
| 4. **What is the disposition outcome?** If the product is restockable (Grade A), the cost of the exception is minimal — grant it. If it's Grade C or worse, the exception costs real margin. | ||
| 5. **Does granting create a precedent risk?** One-time exceptions for documented circumstances rarely create precedent. Publicised exceptions (social media complaints) always do. | ||
|
|
||
| ## Key Edge Cases | ||
|
|
||
| These are situations where standard workflows fail. Brief summaries — see [edge-cases.md](references/edge-cases.md) for full analysis. | ||
|
|
||
| 1. **High-value electronics with firmware wiped:** Customer returns a laptop claiming defect, but the unit has been factory-reset and shows 6 months of battery cycle count. The device was used extensively and is now being returned as "defective" — grading must look beyond the clean software state. | ||
|
|
||
| 2. **Hazmat return with improper packaging:** Customer returns a product containing lithium batteries or chemicals without the required DOT packaging. Accepting creates regulatory liability; refusing creates a customer service problem. The product cannot go back through standard parcel return shipping. | ||
|
|
||
| 3. **Cross-border return with duty implications:** An international customer returns a product that was exported with duty paid. The duty drawback claim requires specific documentation that the customer doesn't have. The return shipping cost may exceed the product value. | ||
|
|
||
| 4. **Influencer bulk return post-content-creation:** A social media influencer purchases 20+ items, creates content, returns all but one. Technically within policy, but the brand value was extracted. Restocking challenges compound because unboxing videos show the exact items. | ||
|
|
||
| 5. **Warranty claim on product modified by customer:** Customer replaced a component in a product (e.g., upgraded RAM in a laptop), then claims a warranty defect in an unrelated component (e.g., screen failure). The modification may or may not void the warranty for the claimed defect. | ||
|
|
||
| 6. **Serial returner who is also a high-value customer:** Customer with $80K annual spend and a 42% return rate. Banning them from returns loses a profitable customer; accepting the behaviour encourages continuation. Requires nuanced segmentation beyond simple return rate. | ||
|
|
||
| 7. **Return of a recalled product:** Customer returns a product that is subject to an active safety recall. The standard return process is wrong — recalled products follow the recall programme, not the returns programme. Mixing them creates liability and reporting errors. | ||
|
|
||
| 8. **Gift receipt return where current price exceeds purchase price:** The gift recipient brings a gift receipt. The item is now selling for $30 more than the gift-giver paid. Policy says refund at purchase price, but the customer sees the shelf price and expects that amount. | ||
|
|
||
| ## Communication Patterns | ||
|
|
||
| ### Tone Calibration | ||
|
|
||
| - **Standard refund confirmation:** Warm, efficient. Lead with the resolution amount and timeline, not the process. | ||
| - **Denial of return:** Empathetic but clear. Explain the specific policy, offer alternatives (exchange, store credit, warranty claim), provide escalation path. Never leave the customer with no options. | ||
| - **Fraud investigation hold:** Neutral, factual. "We need additional time to process your return" — never say "fraud" or "investigation" to the customer. Provide a timeline. Internal communications are where you document the fraud indicators. | ||
| - **Restocking fee explanation:** Transparent. Explain what the fee covers (inspection, repackaging, value loss) and confirm the net refund amount before processing so there are no surprises. | ||
| - **Vendor RTV claim:** Professional, evidence-based. Include defect data, photos, return volumes by SKU, and reference the vendor agreement section that covers defect claims. | ||
|
|
||
| ### Key Templates | ||
|
|
||
| Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md). | ||
|
|
||
| **RMA approval:** Subject: `Return Approved — Order #{order_id}`. Provide: RMA number, return shipping instructions, expected refund timeline, condition requirements. | ||
|
|
||
| **Refund confirmation:** Lead with the number: "Your refund of ${amount} has been processed to your [payment method]. Please allow [X] business days." | ||
|
|
||
| **Fraud hold notice:** "Your return is being reviewed by our processing team. We expect to have an update within [X] business days. We appreciate your patience." | ||
|
|
||
| ## Escalation Protocols | ||
|
|
||
| ### Automatic Escalation Triggers | ||
|
|
||
| | Trigger | Action | Timeline | | ||
| |---|---|---| | ||
| | Return value > $5,000 (single item) | Supervisor approval required before refund | Before processing | | ||
| | Fraud score ≥ 80 | Hold refund, route to fraud review team | Immediately | | ||
| | Customer has filed chargeback simultaneously | Halt return processing, coordinate with payments team | Within 1 hour | | ||
| | Product identified as recalled | Route to recall coordinator, do not process as standard return | Immediately | | ||
| | Vendor defect rate exceeds 5% for SKU | Notify merchandise and vendor management | Within 24 hours | | ||
| | Third policy exception request from same customer in 12 months | Manager review before granting | Before processing | | ||
| | Suspected counterfeit in return stream | Pull from processing, photograph, notify LP and brand protection | Immediately | | ||
| | Return involves regulated product (pharma, hazmat, medical device) | Route to compliance team | Immediately | | ||
|
|
||
| ### Escalation Chain | ||
|
|
||
| Level 1 (Returns Associate) → Level 2 (Team Lead, 2 hours) → Level 3 (Returns Manager, 8 hours) → Level 4 (Director of Operations, 24 hours) → Level 5 (VP, 48+ hours or any single-item return > $25K) | ||
|
|
||
| ## Performance Indicators | ||
|
|
||
| | Metric | Target | Red Flag | | ||
| |---|---|---| | ||
| | Return processing time (receipt to refund) | < 48 hours | > 96 hours | | ||
| | Inspection accuracy (grade agreement on audit) | > 95% | < 88% | | ||
| | Restock rate (% of returns restocked as new/open box) | > 45% | < 30% | | ||
| | Fraud detection rate (confirmed fraud caught) | > 80% | < 60% | | ||
| | False positive rate (legitimate returns flagged) | < 3% | > 8% | | ||
| | Vendor recovery rate ($ recovered / $ eligible) | > 70% | < 45% | | ||
| | Customer satisfaction (post-return CSAT) | > 4.2/5.0 | < 3.5/5.0 | | ||
| | Cost per return processed | < $8.00 | > $15.00 | | ||
|
|
||
| ## Additional Resources | ||
|
|
||
| - For detailed disposition trees, fraud scoring, vendor recovery frameworks, and grading standards, see [decision-frameworks.md](references/decision-frameworks.md) | ||
| - For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md) | ||
| - For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md) |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Missing required sections: When to Use, How It Works, and Examples (applies to all 8 files).
The coding guidelines and retrieved learnings specify that skill documents must contain these three named sections. None of the eight new files include them. The existing content (description frontmatter, Role and Context, Decision Frameworks, Key Edge Cases) partially covers the intent but does not satisfy the structural requirement.
Consider restructuring each skill to add:
+## When to Use
+<!-- surface the "Use when…" prose already in the frontmatter description here -->
+## How It Works
+<!-- brief overview of the skill's reasoning process -->
+## Examples
+<!-- one or two concrete worked examples showing the skill in action -->As per coding guidelines: "skills/**/*.md: Skills should be formatted as Markdown with clear sections for When to Use, How It Works, and Examples." Based on learnings: "Applies to skills/**/*.md: Skills should be formatted as Markdown with clear sections for When to Use, How It Works, and Examples."
🧰 Tools
🪛 LanguageTool
[style] ~49-~49: ‘almost never’ might be wordy. Consider a shorter alternative.
Context: .... Cosmetics and personal care items are almost never restockable once opened due to health r...
(EN_WORDINESS_PREMIUM_ALMOST_NEVER)
[style] ~57-~57: The double modal “Requires dedicated” is nonstandard (only accepted in certain dialects). Consider “to be dedicated”.
Context: ...r tools, and small appliances. Requires dedicated refurb station, spare parts inventory, ...
(NEEDS_FIXED)
[style] ~116-~116: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...ignal | | Return from address different than shipping address | +10 | Gift returns e...
(DIFFERENT_THAN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` around lines 20 - 217, The file is
missing the mandated top-level Markdown sections "When to Use", "How It Works",
and "Examples"; insert three clearly headed sections into SKILL.md (and the
other seven skill files) after the existing "Role and Context" or before "Core
Knowledge" so the document structure matches the skills guideline; under "When
to Use" state the scenarios/triggers for applying this skill (e.g., returns
exceeding threshold, international returns, recalled items), under "How It
Works" outline the step-by-step workflow and decision points (reference existing
subsections like "Returns Policy Logic", "Inspection and Grading", "Disposition
Decision Trees", "Fraud Scoring Model"), and under "Examples" add 3–5 concrete,
short examples or YAML-like use cases (e.g., Grade A electronics restock flow,
hazmat return refusal, influencer bulk return) to illustrate application.
Adds eval-verified skills for logistics, manufacturing, retail, and energy operations. Each codifies 15+ years of real industry expertise. Source: https://github.com/ai-evos/agent-skills License: Apache-2.0 Co-authored-by: Cursor <[email protected]>
nocodemf
changed the title
Contributor
There was a problem hiding this comment.
Actionable comments posted: 13
♻️ Duplicate comments (1)
skills/returns-reverse-logistics/SKILL.md (1)
1-27: Previously raised structural issues still apply (filename + required section headings).No new information beyond prior feedback; existing comments on naming convention and required
When to Use/How It Works/Examplessections remain valid.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` around lines 1 - 27, The SKILL.md file (skill name "returns-reverse-logistics") is missing required structural headings and may not follow naming conventions; update the frontmatter name to follow the project's naming convention and add the required sections "When to Use", "How It Works", and "Examples" under the "# Returns & Reverse Logistics" content so the document meets template expectations—ensure each new section contains a short descriptive paragraph and at least one practical example or usage scenario, and keep section titles exactly "When to Use", "How It Works", and "Examples" to match validation rules.
🧹 Nitpick comments (1)
skills/returns-reverse-logistics/SKILL.md (1)
117-117: Prefer “different from” in policy table text.Small wording polish: “different from” reads more standard than “different than” here.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` at line 117, Update the policy table cell text that currently reads "Return from address different than shipping address" to use the preferred phrasing "Return from address different from shipping address" (edit the table row in SKILL.md where that exact phrase appears).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/carrier-relationship-management/SKILL.md`:
- Line 1: Rename the file currently named SKILL.md to follow the repository
naming convention (use all lowercase with hyphens); for this skill rename
SKILL.md to carrier-relationship-management.md, and update any references to
SKILL.md elsewhere (indexes, manifests, README links, or import/require
statements) to point to the new lowercase-hyphen filename so references remain
valid.
- Around line 20-27: Add the three required top-level Markdown sections to this
skill document: insert explicit headings "When to Use", "How It Works", and
"Examples" below the existing "Core Knowledge" content; under "When to Use"
describe scenarios and triggers for applying this
carrier-relationship-management skill, under "How It Works" document the
step-by-step process and systems involved (TMS, rate platforms, onboarding,
FMCSA checks, scorecards), and under "Examples" provide 2–3 concrete use cases
or sample workflows (e.g., onboarding a new carrier, running an RFP,
reallocating during tight capacity) so the file conforms to the skills/**/*.md
guideline.
In `@skills/customs-trade-compliance/SKILL.md`:
- Around line 21-27: The SKILL.md for the Customs & Trade Compliance skill is
missing the required "When to Use", "How It Works", and "Examples" sections;
update SKILL.md (the document that currently contains "Role and Context" and
"Core Knowledge") by adding three explicit Markdown headings "## When to Use",
"## How It Works", and "## Examples" after the existing content (place them
where they logically fit, e.g., following "Core Knowledge"), and populate each
with concise guidance: criteria for invoking the skill under "When to Use", a
brief operational overview or workflow under "How It Works", and at least one
concrete usage example under "Examples".
- Line 1: Rename the file skills/customs-trade-compliance/SKILL.md to use
lowercase with hyphens to match the repository convention (e.g.,
skills/customs-trade-compliance/customs-trade-compliance.md or a more specific
hyphenated name as appropriate); update any references or imports that point to
SKILL.md (search for "SKILL.md" in the codebase) so they use the new
lowercase-hyphen filename to avoid broken links.
In `@skills/energy-procurement/SKILL.md`:
- Line 1: The file named SKILL.md must be renamed to follow the repository
convention of lowercase with hyphens; locate SKILL.md and rename it to a
lowercase, hyphenated name that reflects the skill (for example
energy-procurement.md or energy-procurement-skill.md), update any references to
SKILL.md in docs or manifests to the new filename, and ensure the commit
includes only the rename (or a git mv) so history is preserved.
- Around line 21-27: The SKILL.md is missing the mandatory Markdown sections;
add explicit top-level headings "When to Use", "How It Works", and "Examples"
(placed after the existing "Core Knowledge" heading or where appropriate in the
flow) and populate each with concise guidance: "When to Use" should state
scenarios and decision criteria for this skill, "How It Works" should summarize
the procurement lifecycle and key systems/processes (tariff analysis, RFPs,
meter/market data, contract negotiation, demand charge management, PPAs), and
"Examples" should include 2–3 concrete use cases or workflows (e.g., RFP for a
new supplier, demand-charge mitigation during peak season, PPA evaluation) to
illustrate application; keep headings exact so automated checks pick them up.
In `@skills/inventory-demand-planning/SKILL.md`:
- Around line 21-27: The SKILL.md for Inventory Demand Planning is missing the
required sections; add explicit Markdown headings "When to Use", "How It Works",
and "Examples" below the existing "Core Knowledge" section; under "When to Use"
list concise scenarios and constraints where this skill applies (e.g.,
multi-location retailer, SKU count, systems present), under "How It Works"
describe the end-to-end process (data inputs: POS, ERP, WMS, demand planning
suite; forecasting, safety stock, order generation, approvals, PO execution),
and under "Examples" provide 2–3 short concrete examples (e.g., seasonal
promotion planning, DC replenishment for a new SKU, clearance markdown-driven
demand adjustments) so the file conforms to the skills/*.md guideline.
- Line 1: Rename the file skills/inventory-demand-planning/SKILL.md to a
lowercase-hyphen name (e.g.,
skills/inventory-demand-planning/inventory-demand-planning.md) to follow the
repository convention; update any references or links that point to SKILL.md to
the new filename and commit the rename so CI and docs resolve correctly.
In `@skills/production-scheduling/SKILL.md`:
- Line 125: The document mixes British and American spelling (e.g., "optimised"
vs "optimized"); choose one variant (pick either "optimised"/"optimisation" or
"optimized"/"optimization") and replace all occurrences consistently—for
example, change the phrase in the "Validate against due dates" line (and the
occurrence around lines referencing "optimised sequence"/"optimisation") and the
other instance noted (line 214) so the entire SKILL.md uses the same spelling
variant throughout.
- Line 1: Rename the markdown asset currently named SKILL.md to a lowercase
hyphenated filename (production-scheduling.md) to comply with the repository
naming rule; update any references or links that point to SKILL.md (README,
index files, or other markdown docs) to the new production-scheduling.md name
and ensure commits/PR title reflect the rename so CI and docs consumers pick up
the change.
- Around line 21-27: The SKILL.md is missing the required top-level sections;
add three top-level Markdown sections titled "When to Use", "How It Works", and
"Examples" (placed after the existing "Core Knowledge" or immediately under the
header block) and populate them with concise guidance: "When to Use" describing
scenarios and prerequisites for applying Production Scheduling, "How It Works"
explaining the minutes-by-minute sequencing, inputs (work orders, routings,
BOMs), constraints (capacity, changeovers, labour, quality), and interactions
with ERP/MES/CMMS, and "Examples" showing 2–3 practical use cases (e.g.,
resolving a bottleneck, scheduling a mixed-model line, handling a late order).
Ensure headings use Markdown syntax and follow the project's skills/**/*.md
formatting guidelines.
In `@skills/quality-nonconformance/SKILL.md`:
- Line 1: Rename the file currently named "SKILL.md" to follow the repo markdown
naming convention: use lowercase with hyphens; for this skill use
"quality-nonconformance.md" (or another lowercase-hyphen name that reflects the
skill). Update any references to "SKILL.md" within the repo (docs, index, or
manifest) to the new filename so links and imports continue to work.
- Around line 21-27: The SKILL.md is missing required top-level sections; add
explicit Markdown headings "When to Use", "How It Works", and "Examples" as
top-level (##) sections in skills/quality-nonconformance/SKILL.md, placing them
after the existing "Role and Context" and before or around "Core Knowledge" so
the document follows the skills/**/*.md guideline and clearly separates usage
guidance, operational explanation, and concrete examples.
---
Duplicate comments:
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 1-27: The SKILL.md file (skill name "returns-reverse-logistics")
is missing required structural headings and may not follow naming conventions;
update the frontmatter name to follow the project's naming convention and add
the required sections "When to Use", "How It Works", and "Examples" under the "#
Returns & Reverse Logistics" content so the document meets template
expectations—ensure each new section contains a short descriptive paragraph and
at least one practical example or usage scenario, and keep section titles
exactly "When to Use", "How It Works", and "Examples" to match validation rules.
---
Nitpick comments:
In `@skills/returns-reverse-logistics/SKILL.md`:
- Line 117: Update the policy table cell text that currently reads "Return from
address different than shipping address" to use the preferred phrasing "Return
from address different from shipping address" (edit the table row in SKILL.md
where that exact phrase appears).
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
skills/carrier-relationship-management/SKILL.mdskills/customs-trade-compliance/SKILL.mdskills/energy-procurement/SKILL.mdskills/inventory-demand-planning/SKILL.mdskills/logistics-exception-management/SKILL.mdskills/production-scheduling/SKILL.mdskills/quality-nonconformance/SKILL.mdskills/returns-reverse-logistics/SKILL.md
🚧 Files skipped from review as they are similar to previous changes (1)
- skills/logistics-exception-management/SKILL.md
| @@ -0,0 +1,190 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Filename does not follow lowercase-hyphen convention.
Please rename SKILL.md to match repository file naming rules.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/carrier-relationship-management/SKILL.md` at line 1, Rename the file
currently named SKILL.md to follow the repository naming convention (use all
lowercase with hyphens); for this skill rename SKILL.md to
carrier-relationship-management.md, and update any references to SKILL.md
elsewhere (indexes, manifests, README links, or import/require statements) to
point to the new lowercase-hyphen filename so references remain valid.
| @@ -0,0 +1,241 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename SKILL.md to lowercase-hyphen format.
This path does not conform to the markdown filename convention for skills/**.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/customs-trade-compliance/SKILL.md` at line 1, Rename the file
skills/customs-trade-compliance/SKILL.md to use lowercase with hyphens to match
the repository convention (e.g.,
skills/customs-trade-compliance/customs-trade-compliance.md or a more specific
hyphenated name as appropriate); update any references or imports that point to
SKILL.md (search for "SKILL.md" in the codebase) so they use the new
lowercase-hyphen filename to avoid broken links.
| @@ -0,0 +1,205 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Filename should be lowercase with hyphens.
SKILL.md should be renamed to follow the repository filename convention.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/energy-procurement/SKILL.md` at line 1, The file named SKILL.md must
be renamed to follow the repository convention of lowercase with hyphens; locate
SKILL.md and rename it to a lowercase, hyphenated name that reflects the skill
(for example energy-procurement.md or energy-procurement-skill.md), update any
references to SKILL.md in docs or manifests to the new filename, and ensure the
commit includes only the rename (or a git mv) so history is preserved.
| @@ -0,0 +1,216 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename SKILL.md to a lowercase hyphenated filename.
The current filename violates the repository naming rule for markdown assets under skills/**.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/production-scheduling/SKILL.md` at line 1, Rename the markdown asset
currently named SKILL.md to a lowercase hyphenated filename
(production-scheduling.md) to comply with the repository naming rule; update any
references or links that point to SKILL.md (README, index files, or other
markdown docs) to the new production-scheduling.md name and ensure commits/PR
title reflect the rename so CI and docs consumers pick up the change.
| 2. **Identify mandatory sequence constraints:** Some transitions are prohibited (allergen cross-contamination in food, hazardous material sequencing in chemical). These are hard constraints, not optimisable. | ||
| 3. **Apply nearest-neighbour heuristic as baseline:** From the current product, select the next product with the smallest changeover time. This gives a feasible starting sequence. | ||
| 4. **Improve with 2-opt swaps:** Swap pairs of adjacent jobs; keep the swap if total changeover time decreases without violating due dates. | ||
| 5. **Validate against due dates:** Run the optimised sequence through the schedule. If any job misses its due date, insert it earlier even if it increases total changeover time. Due date compliance trumps changeover optimisation. |
Contributor
There was a problem hiding this comment.
Use one English variant consistently (optimization vs optimisation).
The file currently mixes spellings; standardize to one variant for consistency.
Also applies to: 214-214
🧰 Tools
🪛 LanguageTool
[uncategorized] ~125-~125: Do not mix variants of the same word (‘optimisation’ and ‘optimization’) within a single text.
Context: .... Due date compliance trumps changeover optimisation. ### Disruption Re-Sequencing When a ...
(EN_WORD_COHERENCY)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/production-scheduling/SKILL.md` at line 125, The document mixes
British and American spelling (e.g., "optimised" vs "optimized"); choose one
variant (pick either "optimised"/"optimisation" or "optimized"/"optimization")
and replace all occurrences consistently—for example, change the phrase in the
"Validate against due dates" line (and the occurrence around lines referencing
"optimised sequence"/"optimisation") and the other instance noted (line 214) so
the entire SKILL.md uses the same spelling variant throughout.
| @@ -0,0 +1,237 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename file to comply with lowercase-hyphen naming.
The current SKILL.md name violates the repo naming convention for markdown artifacts.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/quality-nonconformance/SKILL.md` at line 1, Rename the file currently
named "SKILL.md" to follow the repo markdown naming convention: use lowercase
with hyphens; for this skill use "quality-nonconformance.md" (or another
lowercase-hyphen name that reflects the skill). Update any references to
"SKILL.md" within the repo (docs, index, or manifest) to the new filename so
links and imports continue to work.
- Rename SKILL.md to <skill-name>.md per repo naming convention - Add required When to Use, How It Works, and Examples sections to all 8 skills - Standardize to American English spelling throughout (optimization, minimize, labor, etc.) - Fix "different than" to "different from" in returns-reverse-logistics Co-authored-by: Cursor <[email protected]>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/logistics-exception-management/logistics-exception-management.md`:
- Around line 12-13: Update the frontmatter key "homepage" which currently
points to "https://github.com/evos-ai/evos-capabilities" so it references the
canonical repository "https://github.com/ai-evos/agent-skills"; locate the
frontmatter block at the top of logistics-exception-management.md and replace
the homepage URL value accordingly.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
skills/carrier-relationship-management/carrier-relationship-management.mdskills/customs-trade-compliance/customs-trade-compliance.mdskills/energy-procurement/energy-procurement.mdskills/inventory-demand-planning/inventory-demand-planning.mdskills/logistics-exception-management/logistics-exception-management.mdskills/production-scheduling/production-scheduling.mdskills/quality-nonconformance/quality-nonconformance.mdskills/returns-reverse-logistics/returns-reverse-logistics.md
Comment on lines
+12
to
+13
| homepage: https://github.com/evos-ai/evos-capabilities | ||
| origin: ECC |
Contributor
There was a problem hiding this comment.
Update frontmatter homepage to the canonical Evos repository URL.
This file points to https://github.com/evos-ai/evos-capabilities, while the PR references https://github.com/ai-evos/agent-skills for the source materials. Please align the URL to avoid dead/outdated links.
🔧 Proposed fix
- homepage: https://github.com/evos-ai/evos-capabilities
+ homepage: https://github.com/ai-evos/agent-skills📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| homepage: https://github.com/evos-ai/evos-capabilities | |
| origin: ECC | |
| homepage: https://github.com/ai-evos/agent-skills | |
| origin: ECC |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/logistics-exception-management/logistics-exception-management.md`
around lines 12 - 13, Update the frontmatter key "homepage" which currently
points to "https://github.com/evos-ai/evos-capabilities" so it references the
canonical repository "https://github.com/ai-evos/agent-skills"; locate the
frontmatter block at the top of logistics-exception-management.md and replace
the homepage URL value accordingly.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
12 issues found across 8 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="skills/returns-reverse-logistics/SKILL.md">
<violation number="1" location="skills/returns-reverse-logistics/SKILL.md:167">
P2: Broken link — `references/edge-cases.md` does not exist in this skill directory (only `SKILL.md` is present). The same applies to the other two reference links (`communication-templates.md`, `decision-frameworks.md`) in the Additional Resources section. Either include these files in the PR or remove the links.</violation>
</file>
<file name="skills/quality-nonconformance/SKILL.md">
<violation number="1" location="skills/quality-nonconformance/SKILL.md:48">
P2: Internal inconsistency: the example labels "7 consecutive points above the center line" as Western Electric Rule 3, but the Core Knowledge section defines Rule 3 as "six consecutive points steadily increasing or decreasing." The scenario matches Rule 2's category (same side of center line), not Rule 3. Since this skill codifies expert knowledge for LLM consumption, a mislabeled rule will produce incorrect SPC guidance.</violation>
<violation number="2" location="skills/quality-nonconformance/SKILL.md:259">
P2: The `references/` directory doesn't exist — all relative links to `references/decision-frameworks.md`, `references/edge-cases.md`, and `references/communication-templates.md` are broken. Either include these reference files in the PR or remove the links.</violation>
</file>
<file name="skills/production-scheduling/SKILL.md">
<violation number="1" location="skills/production-scheduling/SKILL.md:13">
P2: The `homepage` field links to an external repository (`ai-evos/agent-skills`) that isn't controlled by this project. Consider removing this link or pointing it to a vetted location to avoid supply-chain risk.
(Based on your team's feedback about avoiding linking to unvetted external repositories.) [FEEDBACK_USED]</violation>
<violation number="2" location="skills/production-scheduling/SKILL.md:237">
P2: All three `references/` links are broken — the `references/` directory doesn't exist in this skill or anywhere under `skills/`. Either include the referenced files (`decision-frameworks.md`, `edge-cases.md`, `communication-templates.md`) in the PR, or remove the dangling links.</violation>
</file>
<file name="skills/customs-trade-compliance/SKILL.md">
<violation number="1" location="skills/customs-trade-compliance/SKILL.md:13">
P2: The `homepage` field links to an external, unvetted repository (`https://github.com/ai-evos/agent-skills`). Per this project's conventions, external repo links are a supply-chain risk — the preferred pattern is to include referenced content directly in this repo or remove the link.
(Based on your team's feedback about avoiding linking to unvetted external repositories.) [FEEDBACK_USED]</violation>
<violation number="2" location="skills/customs-trade-compliance/SKILL.md:262">
P2: All six `references/` links are broken — the `references/` directory and its files (`decision-frameworks.md`, `edge-cases.md`, `communication-templates.md`) were not included in this PR. The skill text explicitly defers detailed content to these files (e.g., "See decision-frameworks.md for full decision trees"), so they are expected to exist.</violation>
</file>
<file name="skills/carrier-relationship-management/SKILL.md">
<violation number="1" location="skills/carrier-relationship-management/SKILL.md:12">
P2: The `homepage` field points to an external repository (`https://github.com/ai-evos/agent-skills`) that is not controlled by this project. Consider whether this link should be removed or replaced with a reference within this repository.
(Based on your team's feedback about avoiding linking to unvetted external repositories.) [FEEDBACK_USED]</violation>
<violation number="2" location="skills/carrier-relationship-management/SKILL.md:211">
P2: All five `references/` links in this file are broken — the `references/` directory was not included in this PR. Readers following "see [edge-cases.md](references/edge-cases.md) for full analysis" or any of the other four cross-references will hit dead links. Either add the referenced files or remove/update the links.</violation>
</file>
<file name="skills/energy-procurement/SKILL.md">
<violation number="1" location="skills/energy-procurement/SKILL.md:153">
P2: All references to local files under `references/` are broken — the `references/` directory doesn't exist in this skill. The document directs readers to `decision-frameworks.md`, `edge-cases.md`, and `communication-templates.md` for "full analysis," "complete decision framework library," and "full communication templates," but none of these files are included in the PR. Either include the referenced files or remove the dangling links.</violation>
</file>
<file name="skills/logistics-exception-management/SKILL.md">
<violation number="1" location="skills/logistics-exception-management/SKILL.md:221">
P2: All three relative links to `references/` files are broken — no `references/` directory was added in this PR. Users following these links (e.g., for the full edge-case analysis or communication templates) will get 404s. Either add the referenced files or remove the links.</violation>
</file>
<file name="skills/inventory-demand-planning/SKILL.md">
<violation number="1" location="skills/inventory-demand-planning/SKILL.md:246">
P2: All relative links to `references/*.md` are broken — the `references/` directory doesn't exist in this PR. The five links pointing to `edge-cases.md`, `communication-templates.md`, and `decision-frameworks.md` will 404. Either include the referenced files or remove the links.</violation>
</file>
Since this is your first cubic review, here's how it works:
- cubic automatically reviews your code and comments on bugs and improvements
- Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
- Add one-off context when rerunning by tagging
@cubic-dev-aiwith guidance or docs links (includingllms.txt) - Ask questions if you need clarification on any suggestion
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| or balancing manufacturing lines. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/ai-evos/agent-skills |
There was a problem hiding this comment.
P2: The homepage field links to an external repository (ai-evos/agent-skills) that isn't controlled by this project. Consider removing this link or pointing it to a vetted location to avoid supply-chain risk.
(Based on your team's feedback about avoiding linking to unvetted external repositories.)
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/production-scheduling/SKILL.md, line 13:
<comment>The `homepage` field links to an external repository (`ai-evos/agent-skills`) that isn't controlled by this project. Consider removing this link or pointing it to a vetted location to avoid supply-chain risk.
(Based on your team's feedback about avoiding linking to unvetted external repositories.) </comment>
<file context>
@@ -0,0 +1,239 @@
+ or balancing manufacturing lines.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/ai-evos/agent-skills
+origin: ECC
+metadata:
</file context>
| carrier performance, or building freight strategies. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/ai-evos/agent-skills |
There was a problem hiding this comment.
P2: The homepage field points to an external repository (https://github.com/ai-evos/agent-skills) that is not controlled by this project. Consider whether this link should be removed or replaced with a reference within this repository.
(Based on your team's feedback about avoiding linking to unvetted external repositories.)
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/carrier-relationship-management/SKILL.md, line 12:
<comment>The `homepage` field points to an external repository (`https://github.com/ai-evos/agent-skills`) that is not controlled by this project. Consider whether this link should be removed or replaced with a reference within this repository.
(Based on your team's feedback about avoiding linking to unvetted external repositories.) </comment>
<file context>
@@ -0,0 +1,213 @@
+ carrier performance, or building freight strategies.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/ai-evos/agent-skills
+origin: ECC
+metadata:
</file context>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
♻️ Duplicate comments (7)
skills/quality-nonconformance/SKILL.md (1)
1-19:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This is still out of line with the repo naming convention for markdown assets under
skills/**.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/quality-nonconformance/SKILL.md` around lines 1 - 19, The markdown asset file currently named SKILL.md violates the repo naming convention; rename the file to a lowercase hyphenated filename matching the skill name (for example, quality-nonconformance.md) so it follows the `{agents,skills,commands,hooks}/**/*.{md,json}` rule; ensure any references to the file (if any) are updated and the front-matter field `name: quality-nonconformance` remains unchanged.skills/carrier-relationship-management/SKILL.md (1)
1-18:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.The file name still violates the repo convention and should be normalized with the rest of the skill assets.
As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/carrier-relationship-management/SKILL.md` around lines 1 - 18, The file SKILL.md violates the repo naming convention; rename it to a lowercase hyphenated filename that matches the skill name (e.g., carrier-relationship-management.md) and update any internal references or links that point to SKILL.md (check README, index lists, or skill registries). Ensure the frontmatter "name: carrier-relationship-management" remains unchanged and verify CI or tooling that reads the skills directory still finds the file after renaming.skills/returns-reverse-logistics/SKILL.md (1)
1-19:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.The filename is still out of compliance with the repo convention for markdown assets.
As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` around lines 1 - 19, The file is named SKILL.md which violates the repo convention; rename this markdown asset to a lowercase, hyphenated filename that reflects the skill (e.g., rename SKILL.md to returns-reverse-logistics.md) and update any references to this file if present; ensure the frontmatter (name: returns-reverse-logistics) remains unchanged and the file now matches the agents/skills/... lowercase-hyphen naming rule.skills/production-scheduling/SKILL.md (1)
1-19:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This still violates the repository naming rule and keeps the skill packaging inconsistent with the rest of the markdown assets.
As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/production-scheduling/SKILL.md` around lines 1 - 19, The file is named SKILL.md which violates the lowercase-hyphen naming rule; rename the file to production-scheduling.md (lowercase, hyphenated) and ensure any references to SKILL.md in repo docs or index files are updated accordingly; keep the existing frontmatter (name: production-scheduling, metadata, etc.) unchanged while performing the rename so packaging and skill lookup continue to work.skills/customs-trade-compliance/SKILL.md (1)
1-19:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This path still violates the markdown filename convention under
skills/**.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/customs-trade-compliance/SKILL.md` around lines 1 - 19, The markdown filename SKILL.md violates the repository naming convention; rename SKILL.md to a lowercase hyphenated name that matches the skill (e.g., customs-trade-compliance.md), update any references to SKILL.md elsewhere in the repo (docs/indexes, manifest lists, or CI checks) to point to the new filename, and verify the frontmatter "name: customs-trade-compliance" remains correct so the skill metadata continues to align with the new file name.skills/inventory-demand-planning/SKILL.md (1)
1-19:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This naming issue is still unresolved for the skill document.
As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/inventory-demand-planning/SKILL.md` around lines 1 - 19, The file is incorrectly named SKILL.md but the frontmatter "name: inventory-demand-planning" and repo conventions require a lowercase, hyphenated filename; rename skills/inventory-demand-planning/SKILL.md to skills/inventory-demand-planning/inventory-demand-planning.md, update any references/links to that path (docs, README, CI/manifests) so they point to the new filename, and ensure metadata/frontmatter remains unchanged (e.g., the "name" field) after the rename.skills/energy-procurement/SKILL.md (1)
1-19:⚠️ Potential issue | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This file still does not comply with the repository naming convention for markdown assets.
As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/energy-procurement/SKILL.md` around lines 1 - 19, The file SKILL.md violates the repository naming convention; rename SKILL.md to a lowercase, hyphenated filename that matches the skill identity (e.g., energy-procurement.md) so the asset follows the "{agents,skills,commands,hooks}/**/*.{md,json}" rule; update any internal references that point to SKILL.md and ensure the frontmatter (name: energy-procurement) remains unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/carrier-relationship-management/SKILL.md`:
- Line 75: The target mix line ("Target mix: 60-70% asset, 20-30% broker, 5-15%
niche/specialty") is ambiguous because the ranges can sum >100%; update SKILL.md
to state whether "niche/specialty" is a subset of asset or broker or is a
separate third bucket and then either (a) adjust the numeric ranges so the three
buckets collectively total 100% across typical scenarios, or (b) explicitly
indicate that the 5-15% niche/specialty overlaps with asset or broker and show
example allocations (e.g., 60-70% asset including 5-15% niche, 20-30% broker) so
readers aren’t confused.
In `@skills/customs-trade-compliance/SKILL.md`:
- Line 93: The "Valuation impact" sentence that currently reads "**Valuation
impact:** Under CIF/CIP, the customs value includes freight and insurance. Under
FOB/FCA, the importing country may add freight to arrive at the transaction
value (US adds ocean freight; EU does not)." is reversed; update that sentence
so it correctly states that under U.S. CBP transaction value international
freight and insurance are generally excluded from U.S. customs value, while EU
customs valuation typically includes transport and insurance up to the place
where the goods enter the Union (i.e., the EU includes freight/insurance whereas
the U.S. excludes them), and keep the CIF/CIP vs FOB/FCA examples to illustrate
the difference for duty calculation.
In `@skills/inventory-demand-planning/SKILL.md`:
- Around line 127-135: Add an explicit review trigger for the "Event-driven
(weather, local events)" row under the "Review Trigger" column: when external
regressor quality or relevance degrades (e.g., correlation with demand falls
below a threshold such as 0.6) or post-event forecast performance deteriorates
(e.g., WMAPE or absolute error rises >30% for 2 consecutive comparable event
periods), re-evaluate the "Regression with external regressors" method and
consider switching to "Manual override with documented rationale".
In `@skills/quality-nonconformance/SKILL.md`:
- Around line 47-48: The SPC example under the "SPC signal interpretation"
heading that currently reads "7 consecutive points above the center line
(Western Electric Rule 3)" conflicts with your rule definitions later (lines
~94-95); update that sentence to reference the correct rule label used in your
document (or rephrase to "trend rule: 7 consecutive points above the center
line") so it matches the rule set defined below, and ensure any parenthetical
rule number/name exactly matches the rule name used at lines ~94-95.
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 37-40: The workflow text "Receive and inspect item at returns
center; assign condition grade (A through F)" conflicts with the later grading
model that only defines A-D; update the workflow to match the defined scale or
expand the grading model. Specifically, either change the workflow phrase to
"assign condition grade (A through D)" to match the grading model, or add
definitions for grades E and F in the grading model section (the later block
currently defining A-D) so both places use a consistent A–F scale.
---
Duplicate comments:
In `@skills/carrier-relationship-management/SKILL.md`:
- Around line 1-18: The file SKILL.md violates the repo naming convention;
rename it to a lowercase hyphenated filename that matches the skill name (e.g.,
carrier-relationship-management.md) and update any internal references or links
that point to SKILL.md (check README, index lists, or skill registries). Ensure
the frontmatter "name: carrier-relationship-management" remains unchanged and
verify CI or tooling that reads the skills directory still finds the file after
renaming.
In `@skills/customs-trade-compliance/SKILL.md`:
- Around line 1-19: The markdown filename SKILL.md violates the repository
naming convention; rename SKILL.md to a lowercase hyphenated name that matches
the skill (e.g., customs-trade-compliance.md), update any references to SKILL.md
elsewhere in the repo (docs/indexes, manifest lists, or CI checks) to point to
the new filename, and verify the frontmatter "name: customs-trade-compliance"
remains correct so the skill metadata continues to align with the new file name.
In `@skills/energy-procurement/SKILL.md`:
- Around line 1-19: The file SKILL.md violates the repository naming convention;
rename SKILL.md to a lowercase, hyphenated filename that matches the skill
identity (e.g., energy-procurement.md) so the asset follows the
"{agents,skills,commands,hooks}/**/*.{md,json}" rule; update any internal
references that point to SKILL.md and ensure the frontmatter (name:
energy-procurement) remains unchanged.
In `@skills/inventory-demand-planning/SKILL.md`:
- Around line 1-19: The file is incorrectly named SKILL.md but the frontmatter
"name: inventory-demand-planning" and repo conventions require a lowercase,
hyphenated filename; rename skills/inventory-demand-planning/SKILL.md to
skills/inventory-demand-planning/inventory-demand-planning.md, update any
references/links to that path (docs, README, CI/manifests) so they point to the
new filename, and ensure metadata/frontmatter remains unchanged (e.g., the
"name" field) after the rename.
In `@skills/production-scheduling/SKILL.md`:
- Around line 1-19: The file is named SKILL.md which violates the
lowercase-hyphen naming rule; rename the file to production-scheduling.md
(lowercase, hyphenated) and ensure any references to SKILL.md in repo docs or
index files are updated accordingly; keep the existing frontmatter (name:
production-scheduling, metadata, etc.) unchanged while performing the rename so
packaging and skill lookup continue to work.
In `@skills/quality-nonconformance/SKILL.md`:
- Around line 1-19: The markdown asset file currently named SKILL.md violates
the repo naming convention; rename the file to a lowercase hyphenated filename
matching the skill name (for example, quality-nonconformance.md) so it follows
the `{agents,skills,commands,hooks}/**/*.{md,json}` rule; ensure any references
to the file (if any) are updated and the front-matter field `name:
quality-nonconformance` remains unchanged.
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 1-19: The file is named SKILL.md which violates the repo
convention; rename this markdown asset to a lowercase, hyphenated filename that
reflects the skill (e.g., rename SKILL.md to returns-reverse-logistics.md) and
update any references to this file if present; ensure the frontmatter (name:
returns-reverse-logistics) remains unchanged and the file now matches the
agents/skills/... lowercase-hyphen naming rule.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fed7366a-2b80-44a8-b574-99998576ae97
📒 Files selected for processing (8)
skills/carrier-relationship-management/SKILL.mdskills/customs-trade-compliance/SKILL.mdskills/energy-procurement/SKILL.mdskills/inventory-demand-planning/SKILL.mdskills/logistics-exception-management/SKILL.mdskills/production-scheduling/SKILL.mdskills/quality-nonconformance/SKILL.mdskills/returns-reverse-logistics/SKILL.md
✅ Files skipped from review due to trivial changes (1)
- skills/logistics-exception-management/SKILL.md
There was a problem hiding this comment.
1 issue found across 8 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="skills/carrier-relationship-management/SKILL.md">
<violation number="1" location="skills/carrier-relationship-management/SKILL.md:173">
P2: "Use the templates below" references templates that don't exist in the document. The original link to `references/communication-templates.md` was removed but the templates were never inlined. Either add the actual communication templates or change this to something like "Use the patterns above as a base…".</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (10)
skills/returns-reverse-logistics/SKILL.md (2)
1-19: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This file still violates the repository naming convention for markdown assets under
skills/**. Please rename it to something likereturns-reverse-logistics.mdand update any references that still use the current filename.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` around lines 1 - 19, The file SKILL.md violates the repo naming convention; rename SKILL.md to a lowercase hyphenated filename (e.g., returns-reverse-logistics.md) and update any references that point to SKILL.md (search for "SKILL.md" across the repo and replace with the new filename), and ensure metadata/frontmatter (name: returns-reverse-logistics) remains consistent with the new filename; also update any tooling/config that explicitly lists or imports SKILL.md.
35-40:⚠️ Potential issue | 🟡 MinorMake the grading scale consistent.
Line 39 says inspection assigns grades
A through F, but the grading model below only definesA-D. Align these sections so the workflow does not point reviewers to undefined grades.Also applies to: 68-72
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` around lines 35 - 40, The workflow text "Receive and inspect item at returns center; assign condition grade (A through F)" conflicts with the grading model that only defines A–D; either change that phrase to "A through D" or expand the grading model to define E and F as well so both sections match; update every occurrence (including the grading model block and the workflow line) to use the same grade range to avoid undefined grades.skills/inventory-demand-planning/SKILL.md (2)
1-19: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.The content now follows the required skill structure, but the file path still does not follow the repo naming convention. Please rename it to something like
inventory-demand-planning.mdand update any references that still point toSKILL.md.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/inventory-demand-planning/SKILL.md` around lines 1 - 19, The file is named SKILL.md which violates the lowercase-hyphenated naming convention; rename the file from SKILL.md to inventory-demand-planning.md and update any references (documentation, indexes, or links) that point to SKILL.md to use inventory-demand-planning.md, ensuring metadata front-matter (name: inventory-demand-planning) remains unchanged and CI/docs references that load skills (e.g., any registry or README entries) are updated accordingly.
127-135:⚠️ Potential issue | 🟡 MinorFill in the missing review trigger for the
Event-drivenrow.Every other demand pattern row tells the reader when to re-evaluate the method, but this one is blank. Add an explicit trigger so the table stays actionable for weather/event-driven forecasts.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/inventory-demand-planning/SKILL.md` around lines 127 - 135, For the table row "Event-driven (weather, local events)" add an explicit review trigger in the "Review Trigger" column stating when to re-evaluate the method—e.g., "When external regressor effectiveness degrades (correlation with demand < 0.6) or post-event WMAPE > 30% for two consecutive events, or new/unmodeled event types emerge"—so the "Event-driven" row has a clear, actionable re-evaluation condition.skills/carrier-relationship-management/SKILL.md (2)
1-18: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This markdown asset still does not follow the repository naming convention. Please rename it to something like
carrier-relationship-management.mdand update any links or references that still point atSKILL.md.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/carrier-relationship-management/SKILL.md` around lines 1 - 18, The file is misnamed as SKILL.md and must follow the repo convention of lowercase hyphenated filenames; rename SKILL.md to carrier-relationship-management.md and update all references to SKILL.md across the repo (search for literal "SKILL.md" in docs, README, skills manifests and any import/link paths). Ensure the file front-matter (name: carrier-relationship-management) remains unchanged and that any hyperlinks or tooling that referenced SKILL.md are updated to the new filename so links resolve correctly.
73-76:⚠️ Potential issue | 🟡 MinorClarify whether
niche/specialtyis a subset or a third bucket.The guidance currently reads as three independent percentages, but the stated ranges can add up to 115%. Either make
niche/specialtyan explicit subset of asset/broker capacity or rebalance the ranges so the buckets total 100%.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/carrier-relationship-management/SKILL.md` around lines 73 - 76, The three-bucket breakdown under "Asset carriers vs. brokers" is ambiguous and the percentages can sum over 100%; update the copy to either (A) state that "niche/specialty carriers" is a subset of asset or broker capacity (e.g., "5–15% of your asset carrier allocation reserved for niche/specialty") or (B) rebalance the three buckets to explicitly total 100% (e.g., 60–70% asset, 25–35% brokers, 5–10% niche/specialty) and adjust the explanatory sentence accordingly; make the change in the "Asset carriers vs. brokers" paragraph and the listed percentage examples so the relationship of "niche/specialty" to the other buckets is unambiguous.skills/energy-procurement/SKILL.md (1)
1-19: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This file still does not comply with the repository naming convention for markdown assets. Please rename it to something like
energy-procurement.mdand update any references to the current filename.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/energy-procurement/SKILL.md` around lines 1 - 19, Rename the markdown asset file SKILL.md to a lowercase hyphenated name such as energy-procurement.md and update all references to SKILL.md (e.g., in README, index files, skill registries or imports) to the new filename; ensure the frontmatter stays unchanged and run a quick grep across the repo for "SKILL.md" to catch and replace any occurrences so the repository follows the `{agents,skills,commands,hooks}/**/*.{md,json}` naming convention.skills/quality-nonconformance/SKILL.md (1)
1-19: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.The document structure is now in good shape, but the filename still breaks the repo naming convention for markdown assets. Please rename it to something like
quality-nonconformance.mdand update any links that reference the current path.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/quality-nonconformance/SKILL.md` around lines 1 - 19, The file SKILL.md should be renamed to follow lowercase-hyphen convention; rename SKILL.md to quality-nonconformance.md and update every reference to SKILL.md (links, README entries, or any import/manifest that points to skills/quality-nonconformance/SKILL.md) to use skills/quality-nonconformance/quality-nonconformance.md so repository naming rules for markdown assets are preserved.skills/production-scheduling/SKILL.md (1)
1-19: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.This file still violates the repository naming rule for markdown assets under
skills/**. Please rename it to something likeproduction-scheduling.mdand update any references that still point atSKILL.md.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/production-scheduling/SKILL.md` around lines 1 - 19, The file currently named SKILL.md must be renamed to a lowercase hyphenated markdown filename (e.g., production-scheduling.md) to comply with the repository naming rule; update the frontmatter and any references/imports that point to SKILL.md (search for "SKILL.md" and the skill name "production-scheduling") so links, documentation, and CI that reference the old filename now point to production-scheduling.md and ensure no remaining references use uppercase or underscores.skills/customs-trade-compliance/SKILL.md (1)
1-19: 🛠️ Refactor suggestion | 🟠 MajorRename
SKILL.mdto a lowercase hyphenated filename.The document content is structured correctly now, but the filename still violates the repo naming convention for markdown assets. Please rename it to something like
customs-trade-compliance.mdand update any references to the old path.As per coding guidelines: "
{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g.,python-reviewer.md,tdd-workflow.md)."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/customs-trade-compliance/SKILL.md` around lines 1 - 19, Rename the markdown asset file from SKILL.md to a lowercase hyphenated name like customs-trade-compliance.md and update all references to the old filename/path (including any imports, links, or manifests that mention "SKILL.md" or the skill identifier "customs-trade-compliance") so the frontmatter name/metadata remains unchanged and repo naming conventions for agents/skills markdown assets are satisfied.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/logistics-exception-management/SKILL.md`:
- Around line 1-18: The SKILL.md file name violates the repo convention; rename
the file from SKILL.md to a lowercase hyphenated name such as
logistics-exception-management.md (the document's "name:
logistics-exception-management" identifies the intended slug) and update all
references/imports that point to SKILL.md (search for "SKILL.md" and any links)
so they now reference logistics-exception-management.md; ensure any tooling or
metadata that expects the filename (e.g., clawdbot/emoji usage) continues to
work after the rename.
---
Duplicate comments:
In `@skills/carrier-relationship-management/SKILL.md`:
- Around line 1-18: The file is misnamed as SKILL.md and must follow the repo
convention of lowercase hyphenated filenames; rename SKILL.md to
carrier-relationship-management.md and update all references to SKILL.md across
the repo (search for literal "SKILL.md" in docs, README, skills manifests and
any import/link paths). Ensure the file front-matter (name:
carrier-relationship-management) remains unchanged and that any hyperlinks or
tooling that referenced SKILL.md are updated to the new filename so links
resolve correctly.
- Around line 73-76: The three-bucket breakdown under "Asset carriers vs.
brokers" is ambiguous and the percentages can sum over 100%; update the copy to
either (A) state that "niche/specialty carriers" is a subset of asset or broker
capacity (e.g., "5–15% of your asset carrier allocation reserved for
niche/specialty") or (B) rebalance the three buckets to explicitly total 100%
(e.g., 60–70% asset, 25–35% brokers, 5–10% niche/specialty) and adjust the
explanatory sentence accordingly; make the change in the "Asset carriers vs.
brokers" paragraph and the listed percentage examples so the relationship of
"niche/specialty" to the other buckets is unambiguous.
In `@skills/customs-trade-compliance/SKILL.md`:
- Around line 1-19: Rename the markdown asset file from SKILL.md to a lowercase
hyphenated name like customs-trade-compliance.md and update all references to
the old filename/path (including any imports, links, or manifests that mention
"SKILL.md" or the skill identifier "customs-trade-compliance") so the
frontmatter name/metadata remains unchanged and repo naming conventions for
agents/skills markdown assets are satisfied.
In `@skills/energy-procurement/SKILL.md`:
- Around line 1-19: Rename the markdown asset file SKILL.md to a lowercase
hyphenated name such as energy-procurement.md and update all references to
SKILL.md (e.g., in README, index files, skill registries or imports) to the new
filename; ensure the frontmatter stays unchanged and run a quick grep across the
repo for "SKILL.md" to catch and replace any occurrences so the repository
follows the `{agents,skills,commands,hooks}/**/*.{md,json}` naming convention.
In `@skills/inventory-demand-planning/SKILL.md`:
- Around line 1-19: The file is named SKILL.md which violates the
lowercase-hyphenated naming convention; rename the file from SKILL.md to
inventory-demand-planning.md and update any references (documentation, indexes,
or links) that point to SKILL.md to use inventory-demand-planning.md, ensuring
metadata front-matter (name: inventory-demand-planning) remains unchanged and
CI/docs references that load skills (e.g., any registry or README entries) are
updated accordingly.
- Around line 127-135: For the table row "Event-driven (weather, local events)"
add an explicit review trigger in the "Review Trigger" column stating when to
re-evaluate the method—e.g., "When external regressor effectiveness degrades
(correlation with demand < 0.6) or post-event WMAPE > 30% for two consecutive
events, or new/unmodeled event types emerge"—so the "Event-driven" row has a
clear, actionable re-evaluation condition.
In `@skills/production-scheduling/SKILL.md`:
- Around line 1-19: The file currently named SKILL.md must be renamed to a
lowercase hyphenated markdown filename (e.g., production-scheduling.md) to
comply with the repository naming rule; update the frontmatter and any
references/imports that point to SKILL.md (search for "SKILL.md" and the skill
name "production-scheduling") so links, documentation, and CI that reference the
old filename now point to production-scheduling.md and ensure no remaining
references use uppercase or underscores.
In `@skills/quality-nonconformance/SKILL.md`:
- Around line 1-19: The file SKILL.md should be renamed to follow
lowercase-hyphen convention; rename SKILL.md to quality-nonconformance.md and
update every reference to SKILL.md (links, README entries, or any
import/manifest that points to skills/quality-nonconformance/SKILL.md) to use
skills/quality-nonconformance/quality-nonconformance.md so repository naming
rules for markdown assets are preserved.
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 1-19: The file SKILL.md violates the repo naming convention;
rename SKILL.md to a lowercase hyphenated filename (e.g.,
returns-reverse-logistics.md) and update any references that point to SKILL.md
(search for "SKILL.md" across the repo and replace with the new filename), and
ensure metadata/frontmatter (name: returns-reverse-logistics) remains consistent
with the new filename; also update any tooling/config that explicitly lists or
imports SKILL.md.
- Around line 35-40: The workflow text "Receive and inspect item at returns
center; assign condition grade (A through F)" conflicts with the grading model
that only defines A–D; either change that phrase to "A through D" or expand the
grading model to define E and F as well so both sections match; update every
occurrence (including the grading model block and the workflow line) to use the
same grade range to avoid undefined grades.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 107efe43-a137-4fab-84ff-864cc2c4bf38
📒 Files selected for processing (8)
skills/carrier-relationship-management/SKILL.mdskills/customs-trade-compliance/SKILL.mdskills/energy-procurement/SKILL.mdskills/inventory-demand-planning/SKILL.mdskills/logistics-exception-management/SKILL.mdskills/production-scheduling/SKILL.mdskills/quality-nonconformance/SKILL.mdskills/returns-reverse-logistics/SKILL.md
Comment on lines
+1
to
+18
| --- | ||
| name: logistics-exception-management | ||
| description: > | ||
| Codified expertise for handling freight exceptions, shipment delays, | ||
| damages, losses, and carrier disputes. Informed by logistics professionals | ||
| with 15+ years operational experience. Includes escalation protocols, | ||
| carrier-specific behaviors, claims procedures, and judgment frameworks. | ||
| Use when handling shipping exceptions, freight claims, delivery issues, | ||
| or carrier disputes. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/affaan-m/everything-claude-code | ||
| origin: ECC | ||
| metadata: | ||
| author: evos | ||
| clawdbot: | ||
| emoji: "📦" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename SKILL.md to a lowercase hyphenated filename.
This path does not match the repository naming convention for markdown assets under skills/**. Please rename it to something like logistics-exception-management.md and update any references to the old filename.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/logistics-exception-management/SKILL.md` around lines 1 - 18, The
SKILL.md file name violates the repo convention; rename the file from SKILL.md
to a lowercase hyphenated name such as logistics-exception-management.md (the
document's "name: logistics-exception-management" identifies the intended slug)
and update all references/imports that point to SKILL.md (search for "SKILL.md"
and any links) so they now reference logistics-exception-management.md; ensure
any tooling or metadata that expects the filename (e.g., clawdbot/emoji usage)
continues to work after the rename.
11 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds 8 domain-expert operational skills from Evos, covering logistics, manufacturing, retail, and energy operations.
Skills Added
Each skill codifies 15+ years of real industry expertise. Eval-verified with 93.2% average score across 201 scenarios. Full reference materials and eval suites at https://github.com/ai-evos/agent-skills
License: Apache-2.0
Made with Cursor
Summary by CodeRabbit