Skill: ivangdavila/vinted (version 1.0.0)

--- name: Vinted slug: vinted version: 1.0.0 homepage: https://clawic.com/skills/vinted description: Buy and resell on Vinted with listing systems, price discipline, shipping workflows, and trust-first handling for offers, bundles, and disputes. changelog: Initial release with end-to-end Vinted workflows for buying, selling, shipping, bundles, and account-safe dispute handling. metadata: {"clawdbot":{"emoji":"👗","requires":{"bins":[],"config":["~/vinted/"]},"os":["darwin","linux","win32"]}} --- ## When to Use User needs practical Vinted help in real time: sourcing pieces, checking whether a price is fair, writing a listing, managing offers, packing sold items, or resolving shipping and dispute issues. Use this skill when the output must feel like a fashion resale marketplace operator, not a generic ecommerce assistant. ## Architecture Memory lives in `~/vinted/`. If `~/vinted/` does not exist, run `setup.md`. See `memory-template.md` for baseline structure. ```text ~/vinted/ |-- memory.md # Core profile, goals, and operating preferences |-- closet.md # Active inventory, condition notes, and stale-item status |-- sourcing-log.md # Buyer watchlist, target prices, and buy/no-buy decisions |-- listing-lab.md # Listing experiments, copy changes, and outcome notes |-- shipping-log.md # Sold parcels, proof records, and issue timelines |-- incident-log.md # Returns, disputes, fraud attempts, and resolutions `-- pro-notes.md # Business-mode rules, batching, and service standards ``` ## Quick Reference Load only the file needed for the current bottleneck. | Topic | File | |-------|------| | Setup guide | `setup.md` | | Memory structure and status model | `memory-template.md` | | Buyer-side search and decision flow | `buyer-flow.md` | | Closet cleanup and seller operations | `closet-ops.md` | | Listing copy, photos, and conversion diagnostics | `listing-lab.md` | | Pricing, offers, bundles, and visibility spend | `pricing-and-bundles.md` | | Shipping, parcel proof, and claim handling | `shipping-and-claims.md` | | Account safety, authenticity, and scam prevention | `trust-and-safety.md` | | Business-mode operating standards | `pro-ops.md` | | Daily, weekly, and monthly cadence | `operations-rhythm.md` | ## Operating Coverage This skill combines three layers in one execution model: - buyer layer: search, compare, negotiate, and decide with risk and total-cost awareness - seller layer: intake, pricing, listing quality, offers, bundles, shipping, and recovery of stale inventory - systems layer: memory, review rhythm, and optional Pro-grade operating standards for repeatable resale work ## Data Storage Local notes in `~/vinted/` may include: - usage profile, preferred brands, sizing constraints, and budget limits - closet inventory, price floors, stale-item rules, and bundle policy - sourcing outcomes, failed purchases, and fraud red flags worth reusing - parcel proof, issue timelines, and business-mode service standards ## Core Rules ### 1. Lock the Operating Mode First Start each session by identifying the active mode: - buyer - casual seller - pro or high-volume reseller Advice that ignores the mode usually misprices the tradeoff between speed, margin, and effort. ### 2. Price From Sell-Through Reality, Not Wishful Comps Use comparable sold or clearly moving listings, item condition, seasonality, and brand demand to set a realistic range. Do not anchor on the highest visible listing if it has weak sell-through evidence. ### 3. Upgrade the Listing Package Before Cutting Price Fix the full conversion stack before recommending markdowns: - cover photo and lighting - title clarity and search words - condition honesty and measurements - bundle logic and shipping readiness Weak listings make even fair prices look expensive. ### 4. Use Offers, Bundles, and Visibility Tools With Explicit Floors Set a floor price, a bundle discount policy, and a stop rule before accepting offers or paying for extra visibility. Never use bumps or spotlight-style tools to rescue a listing that still has unclear photos, fit, or condition. ### 5. Treat Shipping Proof as Part of the Product For every sold item, preserve the evidence chain: - final item photos - packaging photos - label or drop-off proof - timeline notes when anything goes wrong Good proof turns many disputes from opinion into documentation. ### 6. Keep Money, Shipping, and Messaging Inside Platform Rules Reject flows that move payment, labels, or dispute handling off the marketplace when platform protection matters. Convenience is not worth fraud exposure or account risk. ### 7. Review Inventory and Incidents on a Rhythm Run short daily checks for exceptions and a weekly review for pricing, stale stock, bundle uptake, and dispute patterns. Without cadence, closets get noisy and repeated mistakes compound. ## Vinted Traps - Pricing from dream comps instead of realistic sell-through signals -> items sit, then need deep discounts. - Accepting off-platform payment or courier stories -> fraud risk rises immediately. - Posting weak photos with premium pricing -> low trust and constant lowball offers. - Shipping without timestamped evidence -> weak position when parcels are lost, damaged, or disputed. - Paying for extra visibility on low-quality listings -> spend increases while conversion stays weak. - Mixing casual-declutter logic with business inventory logic -> inconsistent response times and poor margin control. ## External Endpoints Only these endpoints are allowed for this skill; block any non-listed domain unless user explicitly approves it. | Endpoint | Data Sent | Purpose | |----------|-----------|---------| | https://www.vinted.com | user-approved search queries, listing drafts, offer flows, messages, shipping steps, and issue handling actions | Marketplace buying, selling, bundles, labels, and disputes | | https://pro-portal.svc.vinted.com | user-approved catalog and account actions for accounts with Vinted Pro access | Business-mode onboarding and operational workflows | No other data is sent externally. ## Security & Privacy Data that leaves your machine: - none by default from this instruction set - only user-approved Vinted traffic when the user requests live buying, selling, shipping, or Pro operations Data that stays local: - context and operating memory under `~/vinted/` - closet notes, sourcing decisions, parcel proof logs, and issue history This skill does NOT: - ask for sign-in details, card data, or identity documents in plain text - move payments or shipping flows off platform - execute irreversible marketplace actions without explicit confirmation - make hidden outbound requests ## Scope This skill ONLY: - structures end-to-end Vinted buying and resale workflows - converts ambiguous marketplace tasks into clear next actions, guardrails, and review dates - keeps continuity through local memory and focused operating playbooks This skill NEVER: - guarantees sale speed, resale margin, or search exposure - invent item condition, brand authenticity, or shipping events - recommends policy evasion or off-platform workarounds ## Related Skills Install with `clawhub install <slug>` if user confirms: - `ecommerce` - Build full-funnel commerce systems beyond one marketplace. - `buy` - Improve purchase decisions with practical buyer-side execution patterns. - `sell` - Strengthen second-hand selling workflows and negotiation discipline. - `pricing` - Run margin-safe pricing, discount, and offer frameworks. - `market-research` - Validate demand, price ranges, and competitor positioning before scaling. ## Feedback - If useful: `clawhub star vinted` - Stay updated: `clawhub sync`

path: buyer-flow.md
content: # Buyer Flow - Vinted

Use this workflow when the user wants to buy on Vinted without overpaying or walking into avoidable risk.

## 1. Lock the Buy Screen

Collect the minimum that changes the decision:
- exact item type, brand, size, and condition target
- budget range including shipping and protection fees
- urgency: buy now, watch, or browse
- appetite for negotiation and bundle buying

## 2. Build a Shortlist

Filter aggressively:
- right size and category
- clear front photo and usable detail shots
- honest condition wording and visible flaws
- seller profile that does not feel inconsistent with the item

Do not compare ten weak listings. Reduce to three solid finalists.

## 3. Check Total Cost, Not Ask Price

For each finalist, compare:
- item price
- expected shipping cost
- buyer-side protection or service fees shown in checkout
- likely return or dispute friction if the item is wrong

Cheap listings with weak evidence often become expensive mistakes.

## 4. Decide the Offer Strategy

Use three lanes:
- buy now if price is fair and sell-through risk is high
- send offer if the listing is good but leaves margin to negotiate
- watch if the listing is acceptable but incomplete or overpriced

Avoid automatic lowballing. Tie the offer to real condition or market logic.

## 5. Bundle Only When Fit and Condition Are Aligned

Bundle buying works best when:
- same seller
- same size logic
- same category or use case
- photos and condition quality are consistent across pieces

Do not force bundles just to chase small savings.

## Output Template

```text
Best option:
Backup option:
Fair-price range:
Offer recommendation:
Main risk:
Decision: buy now / offer / watch / skip
```


path: closet-ops.md
content: # Closet Ops - Vinted

Use this file for day-to-day selling and closet cleanup on Vinted.

## Intake Sequence

Before listing, normalize the item:
1. identify category, brand, size, and condition
2. note visible flaws and measurements
3. decide if the item should be sold, bundled, or skipped
4. set an ask range and a floor before publishing

If the item fails honesty or margin checks, do not list it.

## Draft in Batches

Batch similar work to reduce sloppy listings:
- photo batch
- measurement batch
- copy batch
- publish batch

Mixed batching creates inconsistent quality and missed defects.

## Response Rules

Reply with the same standard every time:
- answer fit and condition questions directly
- avoid emotional price defense
- confirm what is included in the parcel
- move weak leads to a clear yes or no quickly

Fast clarity beats long chat threads.

## Sold-Item Workflow

Once sold:
1. verify item and accessories one last time
2. capture final-condition photos
3. pack cleanly and save proof
4. log shipment state and watch for exceptions

Do not improvise after the item is sold.

## Stale Inventory Recovery

If a listing stalls, diagnose before discounting:
- weak cover photo
- unclear title or category
- overpriced for condition
- seasonality mismatch
- missing bundle logic

Change the dominant bottleneck, then review again after a defined window.


path: listing-lab.md
content: # Listing Lab - Vinted

Use this playbook when a listing is underperforming or when the user wants a stronger listing before publishing.

## Listing Stack

Treat the listing as one system:
- cover photo
- supporting detail photos
- title opening words
- condition honesty
- measurements and fit notes
- price and bundle logic

Fix the stack in that order for most apparel listings.

## Photo Rules

Prioritize trust:
- bright front image with clean background
- close-ups of fabric, tags, and known flaws
- fit or measurement context when size is likely to be questioned
- avoid filters that distort color or wear

If photos create doubt, price pressure increases.

## Copy Rules

The title should lead with the searchable parts:
- brand
- item type
- size or fit cue
- standout attribute only if real

Descriptions should answer what the buyer would ask next, not repeat filler.

## Condition and Measurement Discipline

Always state:
- condition grade in plain language
- any defect worth mentioning
- key measurements when fit is a likely blocker
- what is and is not included

Omissions create friction later in chat or disputes.

## Rewrite Sequence

When improving a weak listing:
1. fix cover photo
2. fix title opening
3. add missing fit and flaw details
4. review price and bundle logic

Do not cut price first if the listing still feels unclear.


path: memory-template.md
content: # Memory Template - Vinted

Create `~/vinted/memory.md` with this structure:

```markdown
# Vinted Memory

## Status
status: ongoing
version: 1.0.0
last: YYYY-MM-DD
integration: pending | done | declined

## Profile
<!-- Buyer, casual seller, or pro reseller -->
<!-- Categories, brands, sizing rules, and operating style -->

## Current Priorities
<!-- What matters now: sourcing, closet cleanup, margin, speed, shipping, or dispute recovery -->

## Price Rules
<!-- Target ranges, floor logic, bundle discounts, and markdown cadence -->

## Shipping and Service
<!-- Preferred carriers, packaging standards, response-time expectations, and parcel-proof habits -->

## Risks and Incidents
<!-- Fraud signals, dispute history, blocked patterns, and prevention rules -->

## Notes
<!-- Durable observations worth reusing -->

---
*Updated: YYYY-MM-DD*
```

## closet.md Template

Create `~/vinted/closet.md`:

```markdown
# Closet

## Active Listings
- item:
  condition:
  ask_price:
  floor_price:
  status: draft | live | stale | sold
  next_action:

## Stale Inventory
- item:
  days_live:
  likely_issue:
  fix_plan:
```

## sourcing-log.md Template

Create `~/vinted/sourcing-log.md`:

```markdown
# Sourcing Log

## YYYY-MM-DD - [Item]
objective:
ask_price:
target_price:
risk_notes:
decision: buy | watch | skip
reason:
```

## shipping-log.md Template

Create `~/vinted/shipping-log.md`:

```markdown
# Shipping Log

## YYYY-MM-DD - [Order or Item]
buyer:
carrier:
proof_saved:
issue_status: none | delayed | damaged | dispute
next_step:
```

## Status Values

| Value | Meaning | Behavior |
|-------|---------|----------|
| `ongoing` | Default state | Keep learning stable marketplace context |
| `complete` | Context is stable | Reuse defaults unless the user changes direction |
| `paused` | User wants lower overhead | Save only critical updates |
| `never_ask` | User opted out of persistence | Operate statelessly |


path: operations-rhythm.md
content: # Operations Rhythm - Vinted

Use this cadence to keep the closet clean, pricing rational, and incidents visible.

## Daily Checks

- reply to serious buyer questions and unresolved offers
- check sold items waiting for shipment
- review new issues or suspicious conversations
- watch only exceptions, not every listing

Daily work should be short and focused on movement.

## Weekly Checks

- review stale listings and choose keep, refresh, markdown, or bundle
- inspect offer acceptance rate versus floor discipline
- review category or brand pockets with strongest sell-through
- log dispute patterns and prevention rules

Weekly cadence is where most resale quality improves.

## Monthly Checks

- assess what categories deserve more effort
- identify what stock keeps trapping time with weak return
- tighten pricing rules and bundle policy
- decide whether casual mode is drifting into pro mode

Monthly reviews stop clutter from becoming strategy.

## Incident Rhythm

When a problem appears:
1. stabilize the active issue
2. rebuild the evidence timeline
3. choose the smallest safe next action
4. record the prevention rule

Fast action matters, but repeated prevention matters more.


path: pricing-and-bundles.md
content: # Pricing and Bundles - Vinted

Use this file when the user asks what price to set, whether to accept an offer, or how to handle bundles and paid visibility.

## Pricing Baseline

Build a realistic range from:
- brand demand and category liquidity
- item condition and completeness
- seasonality
- speed needed to sell
- seller profile: closet cleanup or repeat reseller

Fair pricing is a range, not one magic number.

## Offer Lanes

Define three numbers before going live:
- ask price
- good-offer line
- hard floor

This prevents emotional negotiation and inconsistent replies.

## Bundle Policy

Bundles work when they increase order value without hiding weak items.

Set a simple rule:
- small discount for two items
- larger but controlled discount for three or more
- no extra discount if one item is already near floor

Document the rule so every bundle decision is consistent.

## Markdown Ladder

For stale stock, reduce in steps:
1. improve listing package
2. wait a defined review window
3. apply a measured cut
4. reassess bundle attractiveness

Large random markdowns train buyers to wait.

## Visibility Spend

If the account offers bumps or wardrobe-level visibility tools, use them only when:
- photos and copy are already strong
- price is inside the fair range
- the item has enough margin to justify the spend

Paid visibility cannot fix a weak offer.

## Decision Template

```text
Ask price:
Good-offer line:
Hard floor:
Bundle rule:
Review date:
```


path: pro-ops.md
content: # Pro Ops - Vinted

Use this file only when the user sells as a business or has access to Vinted Pro features.

## Activation Rule

Start in Pro mode only when the user explicitly operates as a business.
Do not assume Pro workflows for casual closet cleanup.

## Operating Standard

Pro mode needs tighter discipline:
- faster response windows
- cleaner catalog consistency
- documented service rules
- batch intake and shipping routines

What feels optional for a casual seller becomes required for repeatable business output.

## Catalog Segmentation

Group stock by:
- category
- season
- price band
- condition tier

Segmentation prevents premium pieces from being managed with bargain-bin logic.

## Margin and Service Rules

Before scaling activity, define:
- target margin by category
- maximum prep time per item
- acceptable return or issue rate
- minimum proof standard per shipment

If service quality drops as volume rises, slow down before adding more stock.

## Market and Compliance Notes

Vinted Pro availability and business requirements vary by market and account status.
Verify local tax, invoicing, and policy obligations before building volume-dependent workflows.

## Batch Review Template

```text
Inventory added:
Listings published:
Sell-through trend:
Issue count:
Next correction:
```


path: setup.md
content: # Setup - Vinted

Use this file when `~/vinted/` is missing or empty.

## Your Attitude

Act like a practical resale operator who understands both side-hustle closets and disciplined fashion resale.
Be honest about effort, margin, and risk.
Prefer repeatable systems over random hustle.

## Priority Order

### 1. Integration First
Within the first exchanges, clarify activation boundaries:
- Should this skill activate whenever Vinted, resale, closet cleanup, or second-hand fashion selling comes up?
- Should it jump in proactively for pricing, listing, and dispute tasks, or only on explicit request?
- Are there situations where this skill should stay inactive?

Before creating local memory files, ask for permission and explain that you will keep only durable marketplace context.
If the user declines persistence, continue in stateless mode.

### 2. Understand the Current Operating Profile
Capture only the details that materially change advice:
- profile: buyer, closet cleanup seller, or pro reseller
- typical categories, brands, and condition mix
- size constraints, shipping region, and turnaround expectations
- current bottleneck: sourcing, pricing, listing quality, offers, shipping, or disputes

Ask minimally, then move quickly into the active task.

### 3. Calibrate the Working Style
Align support to how the user wants help:
- quick mode: direct recommendation plus one fallback
- audit mode: diagnose the bottleneck first, then rank fixes
- operator mode: set rules, cadence, and logs for repeated execution

If uncertain, default to audit mode for safer decisions.

## What You Save Internally

Save durable context, not raw chat transcripts:
- stable sizing, brand, and budget patterns
- closet rules, price floors, and bundle policy
- shipping preferences and recurring issue patterns
- fraud signals, dispute history, and any business-mode standards

Store data only in `~/vinted/` after user consent.

## Golden Rule

Answer the live Vinted task in the same session while quietly building enough context to make future resale decisions faster and safer.


path: shipping-and-claims.md
content: # Shipping and Claims - Vinted

Use this file when an item sells or when delivery problems appear.

## Before Shipment

Run the same proof sequence every time:
- final photos of front, back, tags, and flaws
- packed-item photo
- label or parcel reference captured
- timestamped note of handoff or drop-off

Proof should be easy to find later, not rebuilt from memory.

## Packing Standard

Pack to survive ordinary transit:
- protect delicate surfaces
- seal against moisture
- avoid overstuffing thin mailers
- match packaging to item shape and value

Good packing is part of trust, not an afterthought.

## Tracking and Exceptions

Watch only for exceptions:
- no movement
- wrong route
- damage report
- buyer says item differs from listing

When an exception appears, freeze assumptions and rebuild the timeline from proof.

## Claim Handling

Structure the issue in this order:
1. what was sold
2. what proof exists
3. what the carrier or platform shows
4. what the buyer claims
5. next best action inside platform rules

Chronology matters more than emotion.

## Fast Escalation Signals

Escalate carefully when:
- parcel status stalls beyond normal expectation
- buyer reports damage that was not visible pre-shipment
- the received item allegedly differs from documented details
- the conversation pushes for off-platform settlement

Never delete proof while an issue is open.


path: trust-and-safety.md
content: # Trust and Safety - Vinted

Use this file when a listing, buyer, seller, or conversation feels wrong.

## Counterfeit and Misrepresentation Checks

Pause and review when you see:
- luxury or hype items with weak proof of authenticity
- inconsistent tags, labels, or packaging details
- condition claims that conflict with photos
- seller behavior that changes after purchase questions

If authenticity confidence is low, skip or relist only with stronger evidence.

## Off-Platform Risk Signals

Treat these as hard warnings:
- payment outside the marketplace
- courier stories that bypass normal labels
- requests to continue on another app before trust is established
- pressure to rush around platform rules

Low friction for the other person usually means high risk for the user.

## Account Safety Rules

- Keep all high-risk negotiation inside platform messaging.
- Do not promise what the listing does not prove.
- Do not hide damage, missing parts, or uncertain fit.
- Do not continue with buyers who repeat scam patterns.

## Business and Policy Boundaries

Block tactics that create account risk:
- misleading condition grading
- prohibited or restricted items
- fake urgency or fake scarcity
- evasive behavior after a dispute starts

Short-term wins that damage trust are not wins.

## No-Go Decision

```text
Risk type:
Evidence quality:
Potential downside:
Safer alternative:
Decision: proceed / hold / skip
```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)