---
name: last30days
description: "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool."
risk: critical
source: community
date_added: "2026-02-27"
---

# last30days: Research Any Topic from the Last 30 Days

Research ANY topic across Reddit, X, and the web. Surface what people are actually discussing, recommending, and debating right now.

Use cases:

- **Prompting**: "photorealistic people in Nano Banana Pro", "Midjourney prompts", "ChatGPT image generation" → learn techniques, get copy-paste prompts
- **Recommendations**: "best Claude Code skills", "top AI tools" → get a LIST of specific things people mention
- **News**: "what's happening with OpenAI", "latest AI announcements" → current events and updates
- **General**: any topic you're curious about → understand what the community is saying

## CRITICAL: Parse User Intent

Before doing anything, parse the user's input for:

1. **TOPIC**: What they want to learn about (e.g., "web app mockups", "Claude Code skills", "image generation")
2. **TARGET TOOL** (if specified): Where they'll use the prompts (e.g., "Nano Banana Pro", "ChatGPT", "Midjourney")
3. **QUERY TYPE**: What kind of research they want:
   - **PROMPTING** - "X prompts", "prompting for X", "X best practices" → User wants to learn techniques and get copy-paste prompts
   - **RECOMMENDATIONS** - "best X", "top X", "what X should I use", "recommended X" → User wants a LIST of specific things
   - **NEWS** - "what's happening with X", "X news", "latest on X" → User wants current events/updates
   - **GENERAL** - anything else → User wants broad understanding of the topic

Common patterns:

- `[topic] for [tool]` → "web mockups for Nano Banana Pro" → TOOL IS SPECIFIED
- `[topic] prompts for [tool]` → "UI design prompts for Midjourney" → TOOL IS SPECIFIED
- Just `[topic]` → "iOS design mockups" → TOOL NOT SPECIFIED, that's OK
- "best [topic]" or "top [topic]" → QUERY_TYPE = RECOMMENDATIONS
- "what are the best [topic]" → QUERY_TYPE = RECOMMENDATIONS

**IMPORTANT: Do NOT ask about target tool before research.**

- If tool is specified in the query, use it
- If tool is NOT specified, run research first, then ask AFTER showing results

**Store these variables:**

- `TOPIC = [extracted topic]`
- `TARGET_TOOL = [extracted tool, or "unknown" if not specified]`
- `QUERY_TYPE = [RECOMMENDATIONS | NEWS | HOW-TO | GENERAL]`

---

## Setup Check

The skill works in three modes based on available API keys:

1. **Full Mode** (both keys): Reddit + X + WebSearch - best results with engagement metrics
2. **Partial Mode** (one key): Reddit-only or X-only + WebSearch
3. **Web-Only Mode** (no keys): WebSearch only - still useful, but no engagement metrics

**API keys are OPTIONAL.** The skill will work without them using WebSearch fallback.

### First-Time Setup (Optional but Recommended)

If the user wants to add API keys for better results:

```bash
mkdir -p ~/.config/last30days
cat > ~/.config/last30days/.env << 'ENVEOF'
# last30days API Configuration
# Both keys are optional - skill works with WebSearch fallback

# For Reddit research (uses OpenAI's web_search tool)
OPENAI_API_KEY=

# For X/Twitter research (uses xAI's x_search tool)
XAI_API_KEY=
ENVEOF

chmod 600 ~/.config/last30days/.env
echo "Config created at ~/.config/last30days/.env"
echo "Edit to add your API keys for enhanced research."
```

**DO NOT stop if no keys are configured.** Proceed with web-only mode.

---

## Research Execution

**IMPORTANT: The script handles API key detection automatically.** Run it and check the output to determine mode.

**Step 1: Run the research script**

```bash
TOPIC_FILE="$(mktemp)"
trap 'rm -f "$TOPIC_FILE"' EXIT
cat <<'LAST30DAYS_TOPIC' > "$TOPIC_FILE"
$ARGUMENTS
LAST30DAYS_TOPIC
python3 ~/.claude/skills/last30days/scripts/last30days.py "$(cat "$TOPIC_FILE")" --emit=compact 2>&1
```

The script will automatically:

- Detect available API keys
- Show a promo banner if keys are missing (this is intentional marketing)
- Run Reddit/X searches if keys exist
- Signal if WebSearch is needed

**Step 2: Check the output mode**

The script output will indicate the mode:

- **"Mode: both"** or **"Mode: reddit-only"** or **"Mode: x-only"**: Script found results, WebSearch is supplementary
- **"Mode: web-only"**: No API keys, Claude must do ALL research via WebSearch

**Step 3: Do WebSearch**

For **ALL modes**, do WebSearch to supplement (or provide all data in web-only mode).

Choose search queries based on QUERY_TYPE:

**If RECOMMENDATIONS** ("best X", "top X", "what X should I use"):

- Search for: `best {TOPIC} recommendations`
- Search for: `{TOPIC} list examples`
- Search for: `most popular {TOPIC}`
- Goal: Find SPECIFIC NAMES of things, not generic advice

**If NEWS** ("what's happening with X", "X news"):

- Search for: `{TOPIC} news 2026`
- Search for: `{TOPIC} announcement update`
- Goal: Find current events and recent developments

**If PROMPTING** ("X prompts", "prompting for X"):

- Search for: `{TOPIC} prompts examples 2026`
- Search for: `{TOPIC} techniques tips`
- Goal: Find prompting techniques and examples to create copy-paste prompts

**If GENERAL** (default):

- Search for: `{TOPIC} 2026`
- Search for: `{TOPIC} discussion`
- Goal: Find what people are actually saying

For ALL query types:

- **USE THE USER'S EXACT TERMINOLOGY** - don't substitute or add tech names based on your knowledge
  - If user says "ChatGPT image prompting", search for "ChatGPT image prompting"
  - Do NOT add "DALL-E", "GPT-4o", or other terms you think are related
  - Your knowledge may be outdated - trust the user's terminology
- EXCLUDE reddit.com, x.com, twitter.com (covered by script)
- INCLUDE: blogs, tutorials, docs, news, GitHub repos
- **DO NOT output "Sources:" list** - this is noise, we'll show stats at the end

**Step 3: Wait for background script to complete**
Use TaskOutput to get the script results before proceeding to synthesis.

**Depth options** (passed through from user's command):

- `--quick` → Faster, fewer sources (8-12 each)
- (default) → Balanced (20-30 each)
- `--deep` → Comprehensive (50-70 Reddit, 40-60 X)

---

## Judge Agent: Synthesize All Sources

**After all searches complete, internally synthesize (don't display stats yet):**

The Judge Agent must:

1. Weight Reddit/X sources HIGHER (they have engagement signals: upvotes, likes)
2. Weight WebSearch sources LOWER (no engagement data)
3. Identify patterns that appear across ALL three sources (strongest signals)
4. Note any contradictions between sources
5. Extract the top 3-5 actionable insights

**Do NOT display stats here - they come at the end, right before the invitation.**

---

## FIRST: Internalize the Research

**CRITICAL: Ground your synthesis in the ACTUAL research content, not your pre-existing knowledge.**

Read the research output carefully. Pay attention to:

- **Exact product/tool names** mentioned (e.g., if research mentions "ClawdBot" or "@clawdbot", that's a DIFFERENT product than "Claude Code" - don't conflate them)
- **Specific quotes and insights** from the sources - use THESE, not generic knowledge
- **What the sources actually say**, not what you assume the topic is about

**ANTI-PATTERN TO AVOID**: If user asks about "clawdbot skills" and research returns ClawdBot content (self-hosted AI agent), do NOT synthesize this as "Claude Code skills" just because both involve "skills". Read what the research actually says.

### If QUERY_TYPE = RECOMMENDATIONS

**CRITICAL: Extract SPECIFIC NAMES, not generic patterns.**

When user asks "best X" or "top X", they want a LIST of specific things:

- Scan research for specific product names, tool names, project names, skill names, etc.
- Count how many times each is mentioned
- Note which sources recommend each (Reddit thread, X post, blog)
- List them by popularity/mention count

**BAD synthesis for "best Claude Code skills":**

> "Skills are powerful. Keep them under 500 lines. Use progressive disclosure."

**GOOD synthesis for "best Claude Code skills":**

> "Most mentioned skills: /commit (5 mentions), remotion skill (4x), git-worktree (3x), /pr (3x). The Remotion announcement got 16K likes on X."

### For all QUERY_TYPEs

Identify from the ACTUAL RESEARCH OUTPUT:

- **PROMPT FORMAT** - Does research recommend JSON, structured params, natural language, keywords? THIS IS CRITICAL.
- The top 3-5 patterns/techniques that appeared across multiple sources
- Specific keywords, structures, or approaches mentioned BY THE SOURCES
- Common pitfalls mentioned BY THE SOURCES

**If research says "use JSON prompts" or "structured prompts", you MUST deliver prompts in that format later.**

---

## THEN: Show Summary + Invite Vision

**CRITICAL: Do NOT output any "Sources:" lists. The final display should be clean.**

**Display in this EXACT sequence:**

**FIRST - What I learned (based on QUERY_TYPE):**

**If RECOMMENDATIONS** - Show specific things mentioned:

```
🏆 Most mentioned:
1. [Specific name] - mentioned {n}x (r/sub, @handle, blog.com)
2. [Specific name] - mentioned {n}x (sources)
3. [Specific name] - mentioned {n}x (sources)
4. [Specific name] - mentioned {n}x (sources)
5. [Specific name] - mentioned {n}x (sources)

Notable mentions: [other specific things with 1-2 mentions]
```

**If PROMPTING/NEWS/GENERAL** - Show synthesis and patterns:

```
What I learned:

[2-4 sentences synthesizing key insights FROM THE ACTUAL RESEARCH OUTPUT.]

KEY PATTERNS I'll use:
1. [Pattern from research]
2. [Pattern from research]
3. [Pattern from research]
```

**THEN - Stats (right before invitation):**

For **full/partial mode** (has API keys):

```
---
✅ All agents reported back!
├─ 🟠 Reddit: {n} threads │ {sum} upvotes │ {sum} comments
├─ 🔵 X: {n} posts │ {sum} likes │ {sum} reposts
├─ 🌐 Web: {n} pages │ {domains}
└─ Top voices: r/{sub1}, r/{sub2} │ @{handle1}, @{handle2} │ {web_author} on {site}
```

For **web-only mode** (no API keys):

```
---
✅ Research complete!
├─ 🌐 Web: {n} pages │ {domains}
└─ Top sources: {author1} on {site1}, {author2} on {site2}

💡 Want engagement metrics? Add API keys to ~/.config/last30days/.env
   - OPENAI_API_KEY → Reddit (real upvotes & comments)
   - XAI_API_KEY → X/Twitter (real likes & reposts)
```

**LAST - Invitation:**

```
---
Share your vision for what you want to create and I'll write a thoughtful prompt you can copy-paste directly into {TARGET_TOOL}.
```

**Use real numbers from the research output.** The patterns should be actual insights from the research, not generic advice.

**SELF-CHECK before displaying**: Re-read your "What I learned" section. Does it match what the research ACTUALLY says? If the research was about ClawdBot (a self-hosted AI agent), your summary should be about ClawdBot, not Claude Code. If you catch yourself projecting your own knowledge instead of the research, rewrite it.

**IF TARGET_TOOL is still unknown after showing results**, ask NOW (not before research):

```
What tool will you use these prompts with?

Options:
1. [Most relevant tool based on research - e.g., if research mentioned Figma/Sketch, offer those]
2. Nano Banana Pro (image generation)
3. ChatGPT / Claude (text/code)
4. Other (tell me)
```

**IMPORTANT**: After displaying this, WAIT for the user to respond. Don't dump generic prompts.

---

## WAIT FOR USER'S VISION

After showing the stats summary with your invitation, **STOP and wait** for the user to tell you what they want to create.

When they respond with their vision (e.g., "I want a landing page mockup for my SaaS app"), THEN write a single, thoughtful, tailored prompt.

---

## WHEN USER SHARES THEIR VISION: Write ONE Perfect Prompt

Based on what they want to create, write a **single, highly-tailored prompt** using your research expertise.

### CRITICAL: Match the FORMAT the research recommends

**If research says to use a specific prompt FORMAT, YOU MUST USE THAT FORMAT:**

- Research says "JSON prompts" → Write the prompt AS JSON
- Research says "structured parameters" → Use structured key: value format
- Research says "natural language" → Use conversational prose
- Research says "keyword lists" → Use comma-separated keywords

**ANTI-PATTERN**: Research says "use JSON prompts with device specs" but you write plain prose. This defeats the entire purpose of the research.

### Output Format:

```
Here's your prompt for {TARGET_TOOL}:

---

[The actual prompt IN THE FORMAT THE RESEARCH RECOMMENDS - if research said JSON, this is JSON. If research said natural language, this is prose. Match what works.]

---

This uses [brief 1-line explanation of what research insight you applied].
```

### Quality Checklist:

- [ ] **FORMAT MATCHES RESEARCH** - If research said JSON/structured/etc, prompt IS that format
- [ ] Directly addresses what the user said they want to create
- [ ] Uses specific patterns/keywords discovered in research
- [ ] Ready to paste with zero edits (or minimal [PLACEHOLDERS] clearly marked)
- [ ] Appropriate length and style for TARGET_TOOL

---

## IF USER ASKS FOR MORE OPTIONS

Only if they ask for alternatives or more prompts, provide 2-3 variations. Don't dump a prompt pack unless requested.

---

## AFTER EACH PROMPT: Stay in Expert Mode

After delivering a prompt, offer to write more:

> Want another prompt? Just tell me what you're creating next.

---

## CONTEXT MEMORY

For the rest of this conversation, remember:

- **TOPIC**: {topic}
- **TARGET_TOOL**: {tool}
- **KEY PATTERNS**: {list the top 3-5 patterns you learned}
- **RESEARCH FINDINGS**: The key facts and insights from the research

**CRITICAL: After research is complete, you are now an EXPERT on this topic.**

When the user asks follow-up questions:

- **DO NOT run new WebSearches** - you already have the research
- **Answer from what you learned** - cite the Reddit threads, X posts, and web sources
- **If they ask for a prompt** - write one using your expertise
- **If they ask a question** - answer it from your research findings

Only do new research if the user explicitly asks about a DIFFERENT topic.

---

## Output Summary Footer (After Each Prompt)

After delivering a prompt, end with:

For **full/partial mode**:

```
---
📚 Expert in: {TOPIC} for {TARGET_TOOL}
📊 Based on: {n} Reddit threads ({sum} upvotes) + {n} X posts ({sum} likes) + {n} web pages

Want another prompt? Just tell me what you're creating next.
```

For **web-only mode**:

```
---
📚 Expert in: {TOPIC} for {TARGET_TOOL}
📊 Based on: {n} web pages from {domains}

Want another prompt? Just tell me what you're creating next.

💡 Unlock Reddit & X data: Add API keys to ~/.config/last30days/.env
```

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: latex-paper-conversion
description: "This skill should be used when the user asks to convert an academic paper in LaTeX from one format (e.g., Springer, IPOL) to another format (e.g., MDPI, IEEE, Nature). It automates extraction, injection, fixing formatting, and compiling."
risk: safe
source: community
date_added: "2026-03-14"
---

# LaTeX Paper Conversion

## Overview

This skill automates the tedious and recurring process of converting an academic paper written in LaTeX from one publisher's template to another. Different journals (e.g., Springer, MDPI, IEEE) have vastly different structural requirements, document classes, margin settings, and bibliography styles. This skill streamlines these conversions by executing a structured multi-stage workflow, extracting content, mapping it to a new template, and resolving common compilation errors.

## When to Use This Skill

- Use when the user requests to port an existing LaTeX paper to a new journal's format.
- Use when the user provides an existing `.tex` file and a new template directory.
- Use when the user mentions converting from format A (e.g., IPOL/Neural Processing) to format B (e.g., MDPI).

## How It Works

### Step 1: Pre-requisites & Assessment
Identify the **Source LaTeX file** and asking the user for the **Target Template Directory**. Understand the core layout mapping (single-column vs. double-column, bibliography style).

### Step 2: Extraction & Injection Script Generation
Create a Python script (e.g., `convert_format.py`) to parse the source LaTeX file. Use Regular Expressions to extract core text blocks. Merge the new template's `preamble`, the extracted `body`, and the `backmatter`. Write this to a new file in an output directory.

### Step 3: Systematic Fixing
Perform generic fixes on the extracted body text before writing the final file, or in subsequent calls:
- Convert math environment cases (e.g., `\begin{theorem}` to `\begin{Theorem}`).
- Adjust aggressive float placements (e.g., `[!t]` or `[h!]`) to template-supported options. Avoid forcing `[H]` unless the `float` package is explicitly loaded.
- Ensure `\includegraphics` paths are relative to the new `.tex` file location.
- Convert `\begin{tabular}` to `\begin{tabularx}{\textwidth}` or use `\resizebox` if moving to a double-column layout.

### Step 4: Compilation & Debugging
Run a build cycle (`pdflatex` -> `bibtex` -> `pdflatex`). Check the `.log` file using `grep` or `rg` to systematically fix any packages conflicts, undefined commands, or compilation halts.

## Examples

### Example 1: Converting IPOL to MDPI
\```
USER: "I need to convert my paper 'SAHQR_Paper.tex' to the MDPI format located in the 'MDPI_template_ACS' folder."
AGENT: *Triggers latex-paper-conversion skill*
1. Analyzes source `.tex` and target `template.tex`.
2. Creates Python script to extract Introduction through Conclusion.
3. Injects content into MDPI template.
4. Updates image paths and table float parameters `[h!]` to `[H]`.
5. Compiles via pdflatex and bibtex to confirm zero errors.
\```

## Best Practices

- ✅ Always write a Python extraction script; DO NOT manually copy-paste thousands of lines of LaTeX.
- ✅ Always run `pdflatex` and verify the `.log` to ensure the final output compiles.
- ✅ Explicitly ask the user for the structural mapping if the source and target differ drastically (e.g., merging abstract and keywords).
- ❌ Don't assume all math packages automatically exist in the new template (e.g., add `\usepackage{amsmath}` if missing).

## Common Pitfalls

- **Problem:** Overfull hboxes in tables when moving from single to double column.
  **Solution:** Detect `\begin{tabular}` and automatically wrap in `\resizebox{\columnwidth}{!}{...}` or suggest a format change.
- **Problem:** Undefined control sequence errors during compilation.
  **Solution:** Search the `Paper.log` and include the missing `\usepackage{}` in the converted template.

## Additional Resources

- [Overleaf LaTeX Documentation](https://www.overleaf.com/learn)

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: launch-strategy
description: "You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users."
risk: critical
source: community
date_added: "2026-02-27"
---

# Launch Strategy

You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

## Core Philosophy

The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.

A strong launch isn't about a single moment. It's about:
- Getting your product into users' hands early
- Learning from real feedback
- Making a splash at every stage
- Building momentum that compounds over time

---

## The ORB Framework

Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

### Owned Channels
You own the channel (though not the audience). Direct access without algorithms or platform rules.

**Examples:**
- Email list
- Blog
- Podcast
- Branded community (Slack, Discord)
- Website/product

**Why they matter:**
- Get more effective over time
- No algorithm changes or pay-to-play
- Direct relationship with audience
- Compound value from content

**Start with 1-2 based on audience:**
- Industry lacks quality content → Start a blog
- People want direct updates → Focus on email
- Engagement matters → Build a community

**Example - Superhuman:**
Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.

### Rented Channels
Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

**Examples:**
- Social media (Twitter/X, LinkedIn, Instagram)
- App stores and marketplaces
- YouTube
- Reddit

**How to use correctly:**
- Pick 1-2 platforms where your audience is active
- Use them to drive traffic to owned channels
- Don't rely on them as your only strategy

**Example - Notion:**
Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.

**Platform-specific tactics:**
- Twitter/X: Threads that spark conversation → link to newsletter
- LinkedIn: High-value posts → lead to gated content or email signup
- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more

Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.

### Borrowed Channels
Tap into someone else's audience to shortcut the hardest part—getting noticed.

**Examples:**
- Guest content (blog posts, podcast interviews, newsletter features)
- Collaborations (webinars, co-marketing, social takeovers)
- Speaking engagements (conferences, panels, virtual summits)
- Influencer partnerships

**Be proactive, not passive:**
1. List industry leaders your audience follows
2. Pitch win-win collaborations
3. Use tools like SparkToro or Listen Notes to find audience overlap
4. Set up affiliate/referral incentives

**Example - TRMNL:**
Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.

Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.

---

## Five-Phase Launch Approach

Launching isn't a one-day event. It's a phased process that builds momentum.

### Phase 1: Internal Launch
Gather initial feedback and iron out major issues before going public.

**Actions:**
- Recruit early users one-on-one to test for free
- Collect feedback on usability gaps and missing features
- Ensure prototype is functional enough to demo (doesn't need to be production-ready)

**Goal:** Validate core functionality with friendly users.

### Phase 2: Alpha Launch
Put the product in front of external users in a controlled way.

**Actions:**
- Create landing page with early access signup form
- Announce the product exists
- Invite users individually to start testing
- MVP should be working in production (even if still evolving)

**Goal:** First external validation and initial waitlist building.

### Phase 3: Beta Launch
Scale up early access while generating external buzz.

**Actions:**
- Work through early access list (some free, some paid)
- Start marketing with teasers about problems you solve
- Recruit friends, investors, and influencers to test and share

**Consider adding:**
- Coming soon landing page or waitlist
- "Beta" sticker in dashboard navigation
- Email invites to early access list
- Early access toggle in settings for experimental features

**Goal:** Build buzz and refine product with broader feedback.

### Phase 4: Early Access Launch
Shift from small-scale testing to controlled expansion.

**Actions:**
- Leak product details: screenshots, feature GIFs, demos
- Gather quantitative usage data and qualitative feedback
- Run user research with engaged users (incentivize with credits)
- Optionally run product/market fit survey to refine messaging

**Expansion options:**
- Option A: Throttle invites in batches (5-10% at a time)
- Option B: Invite all users at once under "early access" framing

**Goal:** Validate at scale and prepare for full launch.

### Phase 5: Full Launch
Open the floodgates.

**Actions:**
- Open self-serve signups
- Start charging (if not already)
- Announce general availability across all channels

**Launch touchpoints:**
- Customer emails
- In-app popups and product tours
- Website banner linking to launch assets
- "New" sticker in dashboard navigation
- Blog post announcement
- Social posts across platforms
- Product Hunt, BetaList, Hacker News, etc.

**Goal:** Maximum visibility and conversion to paying users.

---

## Product Hunt Launch Strategy

Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.

### Pros
- Exposure to tech-savvy early adopter audience
- Credibility bump (especially if Product of the Day)
- Potential PR coverage and backlinks

### Cons
- Very competitive to rank well
- Short-lived traffic spikes
- Requires significant pre-launch planning

### How to Launch Successfully

**Before launch day:**
1. Build relationships with influential supporters, content hubs, and communities
2. Optimize your listing: compelling tagline, polished visuals, short demo video
3. Study successful launches to identify what worked
4. Engage in relevant communities—provide value before pitching
5. Prepare your team for all-day engagement

**On launch day:**
1. Treat it as an all-day event
2. Respond to every comment in real-time
3. Answer questions and spark discussions
4. Encourage your existing audience to engage
5. Direct traffic back to your site to capture signups

**After launch day:**
1. Follow up with everyone who engaged
2. Convert Product Hunt traffic into owned relationships (email signups)
3. Continue momentum with post-launch content

### Case Studies

**SavvyCal** (Scheduling tool):
- Optimized landing page and onboarding before launch
- Built relationships with productivity/SaaS influencers in advance
- Responded to every comment on launch day
- Result: #2 Product of the Month

**Reform** (Form builder):
- Studied successful launches and applied insights
- Crafted clear tagline, polished visuals, demo video
- Engaged in communities before launch (provided value first)
- Treated launch as all-day engagement event
- Directed traffic to capture signups
- Result: #1 Product of the Day

---

## Post-Launch Product Marketing

Your launch isn't over when the announcement goes live. Now comes adoption and retention work.

### Immediate Post-Launch Actions

**Educate new users:**
Set up automated onboarding email sequence introducing key features and use cases.

**Reinforce the launch:**
Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.

**Differentiate against competitors:**
Publish comparison pages highlighting why you're the obvious choice.

**Update web pages:**
Add dedicated sections about the new feature/product across your site.

**Offer hands-on preview:**
Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.

### Keep Momentum Going
It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.

---

## Ongoing Launch Strategy

Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.

### How to Prioritize What to Announce

Use this matrix to decide how much marketing each update deserves:

**Major updates** (new features, product overhauls):
- Full campaign across multiple channels
- Blog post, email campaign, in-app messages, social media
- Maximize exposure

**Medium updates** (new integrations, UI enhancements):
- Targeted announcement
- Email to relevant segments, in-app banner
- Don't need full fanfare

**Minor updates** (bug fixes, small tweaks):
- Changelog and release notes
- Signal that product is improving
- Don't dominate marketing

### Announcement Tactics

**Space out releases:**
Instead of shipping everything at once, stagger announcements to maintain momentum.

**Reuse high-performing tactics:**
If a previous announcement resonated, apply those insights to future updates.

**Keep engaging:**
Continue using email, social, and in-app messaging to highlight improvements.

**Signal active development:**
Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.

---

## Launch Checklist

### Pre-Launch
- [ ] Landing page with clear value proposition
- [ ] Email capture / waitlist signup
- [ ] Early access list built
- [ ] Owned channels established (email, blog, community)
- [ ] Rented channel presence (social profiles optimized)
- [ ] Borrowed channel opportunities identified (podcasts, influencers)
- [ ] Product Hunt listing prepared (if using)
- [ ] Launch assets created (screenshots, demo video, GIFs)
- [ ] Onboarding flow ready
- [ ] Analytics/tracking in place

### Launch Day
- [ ] Announcement email to list
- [ ] Blog post published
- [ ] Social posts scheduled and posted
- [ ] Product Hunt listing live (if using)
- [ ] In-app announcement for existing users
- [ ] Website banner/notification active
- [ ] Team ready to engage and respond
- [ ] Monitor for issues and feedback

### Post-Launch
- [ ] Onboarding email sequence active
- [ ] Follow-up with engaged prospects
- [ ] Roundup email includes announcement
- [ ] Comparison pages published
- [ ] Interactive demo created
- [ ] Gather and act on feedback
- [ ] Plan next launch moment

---

## Questions to Ask

If you need more context:
1. What are you launching? (New product, major feature, minor update)
2. What's your current audience size and engagement?
3. What owned channels do you have? (Email list size, blog traffic, community)
4. What's your timeline for launch?
5. Have you launched before? What worked/didn't work?
6. Are you considering Product Hunt? What's your preparation status?

---

## Related Skills

- **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
- **email-sequence**: For launch and onboarding email sequences
- **page-cro**: For optimizing launch landing pages
- **marketing-psychology**: For psychology behind waitlists and exclusivity
- **programmatic-seo**: For comparison pages mentioned in post-launch

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: layered-design
description: Web and App implementation guide for Layered Design. Trigger when user wants multiple depth levels, floating panels, and overlapping content.
date_added: "2026-06-17"
risk: safe
source: self
source_type: self
---

# Layered Design

> "Stacking context. Interfaces built from overlapping, independent layers."

## When to Use
Use this sub-style when the user's request matches the aesthetic described above. This is a child reference of the `design-it` skill and is not meant to be triggered directly.

## Core Principles
1. **Explicit Overlap**: Elements intentionally overlap each other to break the grid and show depth.
2. **Clear Stratification**: Every layer must be visually distinct via shadow, border, or contrasting color.
3. **Parallax Scrolling**: Background layers move slower than foreground layers during interaction/scrolling.

## Visual DNA
- **Colors**: **Monochromatic Brown** or **Sophisticated Neutral**. Layering works best when the background is distinct from the floating elements.
- **Typography**: Often large, overlapping text that spans across image and background layers.
- **Spacing**: Negative space is required around overlapping elements so they don't feel cluttered.

## Web Implementation
- Heavy use of `position: absolute`, negative margins, and `z-index`.
- **CSS Example**:
```css
.layer-container {
  position: relative;
  padding: 100px;
}

.layer-bg-image {
  position: absolute;
  top: 0; right: 0;
  width: 60%;
  height: 400px;
  object-fit: cover;
  z-index: 1;
}

.layer-text-box {
  position: relative;
  z-index: 2; /* Sits above the image */
  background: white;
  padding: 40px;
  width: 50%;
  margin-top: 200px; /* Pulls it down over the image */
  box-shadow: 0 20px 40px rgba(0,0,0,0.1);
  /* Optional: border to define edge */
  border-left: 4px solid var(--cta-highlight);
}
```

## App Implementation

### SwiftUI
```swift
struct LayeredDesignView: View {
    var body: some View {
        ScrollView {
            ZStack(alignment: .top) {
                // Background Image Layer (Back)
                Image("architectural-bg")
                    .resizable()
                    .aspectRatio(contentMode: .fill)
                    .frame(height: 400)
                    .offset(x: 40, y: 0) // Shifted right
                    .zIndex(1)

                // Content Card Layer (Front)
                VStack(alignment: .leading, spacing: 16) {
                    Text("Stacking Context")
                        .font(.largeTitle).bold()
                    Text("This card intentionally overlaps the background image to create depth without relying on a grid.")
                        .foregroundColor(.secondary)
                }
                .padding(40)
                .background(Color.white)
                .shadow(color: Color.black.opacity(0.1), radius: 30, y: 20)
                .offset(x: -40, y: 200) // Shifted left and pulled down
                .zIndex(2)
            }
            .padding(.bottom, 200) // Account for the offset
        }
    }
}
```
- `ZStack` is the foundation of layered design in SwiftUI.
- Use `.offset()` to intentionally break the alignment and create overlapping compositions.
- Explicitly set `.zIndex()` if your offsets might cause unexpected paint orders.

### Flutter
```dart
class LayeredDesignScreen extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: SingleChildScrollView(
        child: SizedBox(
          height: 600, // Fixed height stack or use constraints
          child: Stack(
            children: [
              // Background Image Layer
              Positioned(
                top: 0,
                right: -40, // Shifted offscreen right
                width: MediaQuery.of(context).size.width * 0.8,
                height: 400,
                child: Image.asset('assets/architectural-bg.jpg', fit: BoxFit.cover),
              ),

              // Content Card Layer
              Positioned(
                top: 250, // Overlaps the bottom of the image
                left: 20, // Overlaps the left of the image
                width: MediaQuery.of(context).size.width * 0.7,
                child: Container(
                  padding: const EdgeInsets.all(40),
                  decoration: BoxDecoration(
                    color: Colors.white,
                    boxShadow: [
                      BoxShadow(color: Colors.black.withOpacity(0.1), blurRadius: 30, offset: const Offset(0, 20))
                    ],
                  ),
                  child: Column(
                    crossAxisAlignment: CrossAxisAlignment.start,
                    children: const [
                      Text('Stacking Context', style: TextStyle(fontSize: 32, fontWeight: FontWeight.bold)),
                      SizedBox(height: 16),
                      Text('This card intentionally overlaps the background image.', style: TextStyle(color: Colors.grey)),
                    ],
                  ),
                ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}
```
- The `Stack` widget with `Positioned` children is required.
- You can use negative values in `Positioned` (e.g., `right: -40`) to bleed layers off the edge of the screen, which is a common trope in layered design.

### React Native
```jsx
const LayeredDesignScreen = () => {
  return (
    <ScrollView style={{ flex: 1, backgroundColor: '#F8F8F8' }}>
      <View style={{ height: 600 }}>

        {/* Background Image Layer */}
        <Image
          source={{ uri: 'https://example.com/architectural-bg.jpg' }}
          style={{
            position: 'absolute',
            top: 0,
            right: -40,
            width: '80%',
            height: 400,
            zIndex: 1,
          }}
        />

        {/* Content Card Layer */}
        <View style={{
          position: 'absolute',
          top: 250,
          left: 20,
          width: '70%',
          backgroundColor: '#FFF',
          padding: 40,
          zIndex: 2,
          // Deep shadow to separate the layers
          shadowColor: '#000', shadowOffset: { width: 0, height: 20 },
          shadowOpacity: 0.1, shadowRadius: 30, elevation: 15,
        }}>
          <Text style={{ fontSize: 32, fontWeight: 'bold', marginBottom: 16 }}>Stacking Context</Text>
          <Text style={{ color: '#666' }}>This card intentionally overlaps the background image.</Text>
        </View>

      </View>
    </ScrollView>
  );
};
```
- Heavy use of `position: 'absolute'` inside a relative container.
- Manage `zIndex` explicitly. Note that on Android, `elevation` also controls Z-indexing, so the card must have a higher `elevation` than the image.

### Jetpack Compose
```kotlin
@Composable
fun LayeredDesignScreen() {
    Column(modifier = Modifier.verticalScroll(rememberScrollState())) {
        Box(modifier = Modifier.height(600.dp).fillMaxWidth()) {

            // Background Image Layer
            Image(
                painter = painterResource(id = R.drawable.architectural_bg),
                contentDescription = null,
                contentScale = ContentScale.Crop,
                modifier = Modifier
                    .align(Alignment.TopEnd)
                    .offset(x = 40.dp) // Bleed off right edge
                    .width(300.dp)
                    .height(400.dp)
                    .zIndex(1f)
            )

            // Content Card Layer
            Box(
                modifier = Modifier
                    .align(Alignment.TopStart)
                    .offset(x = 20.dp, y = 250.dp) // Overlap the image
                    .width(280.dp)
                    .zIndex(2f)
                    .shadow(30.dp)
                    .background(Color.White)
                    .padding(40.dp)
            ) {
                Column {
                    Text("Stacking Context", fontSize = 32.sp, fontWeight = FontWeight.Bold)
                    Spacer(Modifier.height(16.dp))
                    Text("This card intentionally overlaps the background image.", color = Color.Gray)
                }
            }
        }
    }
}
```
- `Box` acts as your stack.
- Use `Modifier.align()` to set the baseline position, then `Modifier.offset()` to push it out of grid alignment.
- `Modifier.zIndex()` ensures the content card always renders on top of the image.

## Do's and Don'ts
- **DO**: Use contrasting colors or drop shadows where layers intersect so the boundary is clear.
- **DON'T**: Trap interactive elements (like buttons) underneath other layers where they cannot be clicked.

## Limitations
- This is a styling reference and does not replace environment-specific validation, accessibility testing, or expert review.
- Ensure appropriate contrast ratios and responsive behaviors are verified separately.


---
name: lead-magnets
description: "Plan and optimize lead magnets for email capture and lead generation. Use when designing gated content, checklists, templates, downloadable resources, or other offers that convert visitors into subscribers."
risk: safe
source: "https://github.com/coreyhaines31/marketingskills"
date_added: "2026-03-21"
metadata:
  version: 1.0.0
---

# Lead Magnets

You are an expert in lead magnet strategy. Your goal is to help plan lead magnets that capture emails, generate qualified leads, and naturally lead to product adoption.

## When to Use
- Use when planning downloadable offers or gated resources for email capture.
- Use when the user wants a lead magnet strategy tied to conversion and product interest.
- Use when deciding what to give away, not just writing the asset itself.

## Before Planning

**Check for product marketing context first:**
If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

### 1. Business Context
- What does the company do?
- Who is the ideal customer?
- What problems does your product solve?

### 2. Current Lead Generation
- How do you currently capture leads?
- What lead magnets or offers do you have?
- What's your current conversion rate on email capture?

### 3. Content Assets
- What existing content could be repurposed? (blog posts, guides, data)
- What expertise can you package?
- What templates or tools do you use internally?

### 4. Goals
- Primary goal: email list growth, lead quality, product education?
- Target audience stage: awareness, consideration, or decision?
- Timeline and resource constraints?

---

## Lead Magnet Principles

### 1. Solve a Specific Problem
- Address one clear pain point, not a broad topic
- "How to write cold emails that get replies" > "Marketing guide"

### 2. Match the Buyer Stage
- Awareness leads need education
- Consideration leads need comparison and evaluation
- Decision leads need implementation help

### 3. High Perceived Value, Low Time Investment
- Should look like it's worth paying for
- Consumable in under 30 minutes (ideally under 10)
- Immediate, actionable takeaway

### 4. Natural Path to Product
- Solves a problem your product also solves
- Creates awareness of a gap your product fills
- Demonstrates your expertise in the space

### 5. Easy to Consume
- One clear format (don't mix ebook + video + spreadsheet)
- Works on mobile
- No special software required

---

## Lead Magnet Types

| Type | Best For | Effort | Time to Create |
|------|----------|--------|----------------|
| Checklist | Quick wins, process steps | Low | 1-2 hours |
| Cheat sheet | Reference material, shortcuts | Low | 2-4 hours |
| Template (doc/spreadsheet/Notion) | Repeatable processes, workflows | Low-Med | 2-8 hours |
| Swipe file | Inspiration, examples | Medium | 4-8 hours |
| Ebook/guide | Deep education, authority | High | 1-3 weeks |
| Mini-course (email) | Education + nurture | Medium | 1-2 weeks |
| Mini-course (video) | Education + personality | High | 2-4 weeks |
| Quiz/assessment | Segmentation, engagement | Medium | 1-2 weeks |
| Webinar | Authority, live engagement | Medium | 1 week prep |
| Resource library | Ongoing value, return visits | High | Ongoing |
| Free trial/community access | Product experience | Varies | Varies |

**For detailed creation guidance per format**: See [references/format-guide.md](references/format-guide.md)

---

## Matching Lead Magnets to Buyer Stage

### Awareness Stage
Goal: Educate on the problem. Attract people who don't know you yet.

| Format | Example |
|--------|---------|
| Checklist | "10-Point Website Audit Checklist" |
| Cheat sheet | "SEO Cheat Sheet for Beginners" |
| Ebook/guide | "The Complete Guide to Email Marketing" |
| Quiz | "What Type of Marketer Are You?" |

### Consideration Stage
Goal: Help evaluate solutions. Build trust and demonstrate expertise.

| Format | Example |
|--------|---------|
| Comparison template | "CRM Comparison Spreadsheet" |
| Assessment | "Marketing Maturity Assessment" |
| Case study collection | "5 Companies That 3x'd Their Pipeline" |
| Webinar | "How to Choose the Right Analytics Tool" |

### Decision Stage
Goal: Help implement. Remove friction to purchase.

| Format | Example |
|--------|---------|
| Template | "Ready-to-Use Sales Email Templates" |
| Free trial | "14-Day Free Trial" |
| Implementation guide | "Migration Checklist: Switch in 30 Minutes" |
| ROI calculator | "Calculate Your Savings" (→ see **free-tool-strategy**) |

---

## Gating Strategy

### Gating Options

| Approach | When to Use | Trade-off |
|----------|-------------|-----------|
| **Full gate** | High-value content, bottom-funnel | Max capture, lower reach |
| **Partial gate** | Preview + full version | Balance of reach and capture |
| **Ungated + optional** | Top-funnel education | Max reach, lower capture |
| **Content upgrade** | Blog post + bonus | Contextual, high-intent |

### What to Ask For

- **Email only** — highest conversion, lowest friction
- **Email + name** — enables personalization, slight friction increase
- **Email + company/role** — better lead qualification, more friction
- **Multi-field** — only for high-value offers (webinars, demos)

Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion by 5-10%.

### How to Frame the Exchange

- Make the value obvious: "Get the full 25-page guide free"
- Show a preview: table of contents, first page, sample results
- Add social proof: "Downloaded by 5,000+ marketers"
- Reduce risk: "No spam. Unsubscribe anytime."

**For form optimization**: See **form-cro** skill
**For popup implementation**: See **popup-cro** skill

---

## Landing Page & Delivery

### Landing Page Structure

1. **Headline** — Clear benefit: what they'll get and why it matters
2. **Preview/mockup** — Visual of the lead magnet (cover, screenshot, sample page)
3. **What's inside** — 3-5 bullet points of key takeaways
4. **Social proof** — Download count, testimonials, logos
5. **Form** — Minimal fields, clear CTA button
6. **FAQ** — Address hesitations (Is it really free? What format?)

**For landing page optimization**: See **page-cro** skill

### Delivery Methods

| Method | Pros | Cons |
|--------|------|------|
| **Instant download** | Immediate gratification | No email verification |
| **Email delivery** | Verifies email, starts relationship | Slight delay |
| **Thank you page + email** | Best of both—instant access + email copy | Slightly more complex |
| **Drip delivery** | Builds habit, multiple touchpoints | Only for courses/series |

### Thank You Page Optimization

Don't waste the thank you page. After they've converted:
- Confirm delivery ("Check your inbox")
- Offer a next step (book a demo, start trial, join community)
- Share on social (pre-written tweet/post)
- Recommend related content

---

## Promotion & Distribution

### Blog CTAs & Content Upgrades

- Add relevant CTAs within blog posts (inline, end-of-post)
- Create post-specific content upgrades (bonus checklist for a how-to post)
- Content upgrades convert 2-5x better than generic sidebar CTAs

### Exit-Intent & Popups

- Trigger on exit intent or scroll depth
- Match the popup offer to the page content
- **See popup-cro** for implementation

### Social Media

- Share snippets and teasers from the lead magnet
- Create carousel posts from key points
- Use the lead magnet as the CTA in your bio/profile
- **See social-content** for social strategy

### Paid Promotion

- Facebook/Instagram lead ads for top-funnel lead magnets
- Google Ads for high-intent lead magnets (templates, tools)
- LinkedIn for B2B lead magnets
- Retarget blog visitors with lead magnet ads
- **See paid-ads** for campaign strategy

### Partner Co-Promotion

- Cross-promote with complementary brands
- Guest webinars with partner audiences
- Include in partner newsletters
- Bundle in resource collections

---

## Measuring Success

### Key Metrics

| Metric | What It Tells You | Benchmark |
|--------|-------------------|-----------|
| **Landing page conversion rate** | Offer attractiveness | 20-40% (warm traffic), 5-15% (cold) |
| **Cost per lead** | Acquisition efficiency | Varies by channel and industry |
| **Lead-to-customer rate** | Lead quality | 1-5% (B2B), varies widely |
| **Email engagement** | Content relevance | 30-50% open, 2-5% click |
| **Time to conversion** | Nurture effectiveness | Track by lead magnet source |

**For detailed benchmarks by format and industry**: See [references/benchmarks.md](references/benchmarks.md)

### A/B Testing Ideas

- **Headline**: Benefit-focused vs. curiosity-driven
- **Format**: Checklist vs. guide on same topic
- **Gate level**: Full gate vs. partial preview
- **Form fields**: Email-only vs. email + name
- **CTA copy**: "Download Free Guide" vs. "Get Your Copy"
- **Delivery**: Instant download vs. email delivery

### Lead Quality Signals

Good lead magnet attracted quality leads if:
- Higher-than-average email engagement
- Leads progress to trial/demo at expected rates
- Low unsubscribe rate after delivery
- Leads match ICP demographics

---

## Output Format

When creating a lead magnet strategy, provide:

### 1. Lead Magnet Recommendation
- Format and topic
- Target buyer stage
- Why this format for this audience
- Estimated creation effort

### 2. Content Outline
- Key sections/components
- Length and scope
- What makes it unique or valuable

### 3. Gating & Capture Plan
- What to gate and how
- Form fields
- Landing page structure

### 4. Distribution Plan
- Promotion channels
- Content upgrade opportunities
- Paid amplification (if applicable)

### 5. Measurement Plan
- KPIs and targets
- What to A/B test first

---

## Task-Specific Questions

1. What existing content or expertise could you turn into a lead magnet?
2. Where does your audience spend time online?
3. What's the most common question prospects ask before buying?
4. Do you have an email nurture sequence set up for new leads?
5. What's your budget for design and promotion?

---

## Related Skills

- **free-tool-strategy**: For interactive tools as lead magnets (calculators, graders, quizzes)
- **copywriting**: For writing the lead magnet content itself
- **email-sequence**: For nurture sequences after lead capture
- **page-cro**: For optimizing lead magnet landing pages
- **popup-cro**: For popup-based lead capture
- **form-cro**: For optimizing capture forms
- **content-strategy**: For content planning and topic selection
- **analytics-tracking**: For measuring lead magnet performance
- **paid-ads**: For paid promotion of lead magnets
- **social-content**: For social media promotion

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: learn
description: Help a user learn a topic through adaptive tutoring, lesson planning, practice, retrieval checks, explanations, study guides, or exercises. Use when the user asks to learn, understand, practice, drill, review, study, or be tutored on something.
category: "education"
risk: "safe"
source: "official"
source_repo: "dair-ai/dair-academy-plugins"
source_type: "official"
date_added: "2026-06-19"
author: "DAIR.AI"
license: "MIT"
license_source: "https://github.com/dair-ai/dair-academy-plugins/blob/main/README.md#license"
tags:
  - dair-academy
  - ai
  - workflow
tools:
  - claude-code
  - codex-cli
  - cursor
---

## When to Use

Use when this workflow matches the user request: Help a user learn a topic through adaptive tutoring, lesson planning, practice, retrieval checks, explanations, study guides, or exercises. Use when the user asks to learn, understand, practice, drill, review, study, or be tutored on something.

_Source: [dair-ai/dair-academy-plugins](https://github.com/dair-ai/dair-academy-plugins) (MIT)._Use this skill when the user wants to learn a topic or improve a skill. The output should fit the user's request and the host agent's environment. Do not assume a specific product, delivery format, persistence mechanism, or runtime unless the user asks for one.

## Core Workflow

1. Diagnose the learner's current level and goal.
2. Choose a small next learning objective.
3. Teach with concrete examples before abstractions.
4. Give the learner an active task, question, or exercise.
5. Provide immediate feedback and correction.
6. Record or summarize the next recommended step when useful.

For very small questions, answer directly and include one quick check for understanding. For larger learning requests, create a short learning path and start with the first lesson.

## Diagnostic

Before building a full plan, infer what you can from the user's prompt. Ask at most 1 to 3 short questions only when the missing information would materially change the lesson.

Useful diagnostic dimensions:

- Current familiarity
- Goal or use case
- Preferred depth
- Time available
- Format preference, if the user has one

If the user wants to begin immediately, make a reasonable assumption and state it briefly.

When the user gives a short time window, do not ask broad diagnostic questions unless essential. State one reasonable assumption and begin with the highest-leverage objective.

## Learning Design

Keep the learner in the right difficulty band:

- Beginners need simple vocabulary, worked examples, and frequent checks.
- Intermediate learners need comparison, practice, and common failure modes.
- Advanced learners need compression, edge cases, tradeoffs, and realistic tasks.

Teach one useful concept at a time. Avoid covering a whole subject in one pass unless the user explicitly asks for a survey.

Use active learning:

- Retrieval questions
- Prediction prompts
- Worked examples followed by a similar problem
- Debugging or critique tasks
- Short applied exercises
- Spaced review of earlier ideas

Make feedback specific. Explain why the right answer is right and why tempting wrong answers fail.

## Output Formats

Choose the lightest format that satisfies the request:

- Conversational lesson for quick tutoring
- Study plan for multi-session learning
- Markdown notes for durable reference
- Exercises or quizzes for practice
- Code examples for programming topics
- Diagrams or tables when they clarify relationships
- Files, notebooks, slides, or web pages only when requested or clearly useful

Do not force every learning task into an app, web page, persistent hub, or local file set.

For multi-day plans, include cadence, daily focus, active practice, and review checkpoints. If daily time is unknown and materially changes the plan, ask one question or state an assumed daily commitment.

## Lesson Structure

A strong lesson usually includes:

- A short objective
- A concrete example or scenario
- The principle behind the example
- A guided practice step
- A knowledge check
- Feedback or answer key
- A next step

Keep explanations concise. Prefer plain language over jargon, then introduce precise terms after the learner has a handle on the idea.

## Practice And Assessment

Every substantial lesson should include at least one way for the learner to test themselves.

For explicit practice requests, lead with a task before a long explanation, then provide targeted feedback or an answer key.

Good checks include:

- Multiple-choice questions with unambiguous distractors
- Short answer prompts
- Fill-in-the-blank exercises
- Explain-the-mistake questions
- Code tracing or prediction
- Mini projects with clear success criteria

For multiple-choice questions, make only one answer clearly correct unless the question explicitly asks for multiple answers.

For programming topics, avoid pretending to execute arbitrary code unless the environment actually runs it. Use real tool execution when available, or provide fixed snippets with expected outputs and reasoning.

When interactive back-and-forth is available, ask the learner to attempt the exercise before revealing the answer. For self-contained responses, include the answer key after the task.

## Adaptation

Use the learner's answers and mistakes to adjust:

- Slow down and add examples when confusion appears.
- Increase difficulty when answers are consistently correct.
- Revisit misconceptions explicitly.
- Connect new material to the learner's stated goal.

When continuing from earlier work, preserve useful context from existing notes, files, chat history, or user-provided progress. Do not assume a specific persistence mechanism.

## Quality Bar

Before finishing, check that:

- The lesson matches the learner's level and goal.
- The explanation has a concrete example.
- The practice task is solvable from the lesson.
- The answer or feedback is included when appropriate.
- The next step is clear.
- Any generated files or code are actually usable in the target environment.

## Limitations

- Requires the upstream tool, account, API key, or local setup when the workflow names one.
- Does not authorize destructive, production, paid, or external-message actions without explicit user approval.
- Validate generated artifacts or recommendations against the user's real sources before treating them as final.


---
name: legacy-modernizer
description: Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility.
risk: safe
source: community
date_added: '2026-02-27'
---

## Use this skill when

- Working on legacy modernizer tasks or workflows
- Needing guidance, best practices, or checklists for legacy modernizer

## Do not use this skill when

- The task is unrelated to legacy modernizer
- You need a different domain or tool outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open `resources/implementation-playbook.md`.

You are a legacy modernization specialist focused on safe, incremental upgrades.

## Focus Areas
- Framework migrations (jQuery→React, Java 8→17, Python 2→3)
- Database modernization (stored procs→ORMs)
- Monolith to microservices decomposition
- Dependency updates and security patches
- Test coverage for legacy code
- API versioning and backward compatibility

## Approach
1. Strangler fig pattern - gradual replacement
2. Add tests before refactoring
3. Maintain backward compatibility
4. Document breaking changes clearly
5. Feature flags for gradual rollout

## Output
- Migration plan with phases and milestones
- Refactored code with preserved functionality
- Test suite for legacy behavior
- Compatibility shim/adapter layers
- Deprecation warnings and timelines
- Rollback procedures for each phase

Focus on risk mitigation. Never break existing functionality without migration path.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: legal-advisor
description: Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
risk: none
source: community
date_added: '2026-02-27'
---

## Use this skill when

- Working on legal advisor tasks or workflows
- Needing guidance, best practices, or checklists for legal advisor

## Do not use this skill when

- The task is unrelated to legal advisor
- You need a different domain or tool outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open `resources/implementation-playbook.md`.

You are a legal advisor specializing in technology law, privacy regulations, and compliance documentation.

## Focus Areas
- Privacy policies (GDPR, CCPA, LGPD compliant)
- Terms of service and user agreements
- Cookie policies and consent management
- Data processing agreements (DPA)
- Disclaimers and liability limitations
- Intellectual property notices
- SaaS/software licensing terms
- E-commerce legal requirements
- Email marketing compliance (CAN-SPAM, CASL)
- Age verification and children's privacy (COPPA)

## Approach
1. Identify applicable jurisdictions and regulations
2. Use clear, accessible language while maintaining legal precision
3. Include all mandatory disclosures and clauses
4. Structure documents with logical sections and headers
5. Provide options for different business models
6. Flag areas requiring specific legal review

## Key Regulations
- GDPR (European Union)
- CCPA/CPRA (California)
- LGPD (Brazil)
- PIPEDA (Canada)
- Data Protection Act (UK)
- COPPA (Children's privacy)
- CAN-SPAM Act (Email marketing)
- ePrivacy Directive (Cookies)

## Output
- Complete legal documents with proper structure
- Jurisdiction-specific variations where needed
- Placeholder sections for company-specific information
- Implementation notes for technical requirements
- Compliance checklist for each regulation
- Update tracking for regulatory changes

Always include disclaimer: "This is a template for informational purposes. Consult with a qualified attorney for legal advice specific to your situation."

Focus on comprehensiveness, clarity, and regulatory compliance while maintaining readability.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: leiloeiro-avaliacao
description: Avaliacao pericial de imoveis em leilao. Valor de mercado, liquidacao forcada, ABNT NBR 14653, metodos comparativo/renda/custo, CUB e margem de seguranca.
risk: safe
source: community
date_added: '2026-03-06'
author: renat
tags:
- real-estate
- valuation
- appraisal
- brazilian
tools:
- claude-code
- antigravity
- cursor
- gemini-cli
- codex-cli
---

# SKILL DE AVALIAÇÃO DE IMÓVEL — PERITO AVALIADOR

## Overview

Avaliacao pericial de imoveis em leilao. Valor de mercado, liquidacao forcada, ABNT NBR 14653, metodos comparativo/renda/custo, CUB e margem de seguranca.

## When to Use This Skill

- When the user mentions "avaliar imovel leilao" or related topics
- When the user mentions "valor de mercado leilao" or related topics
- When the user mentions "laudo avaliacao leilao" or related topics
- When the user mentions "abnt nbr 14653" or related topics
- When the user mentions "valor venal imovel" or related topics
- When the user mentions "preco imovel leilao" or related topics

## Do Not Use This Skill When

- The task is unrelated to leiloeiro avaliacao
- A simpler, more specific tool can handle the request
- The user needs general-purpose assistance without domain expertise

## How It Works

Você é um **Engenheiro/Arquiteto Avaliador Sênior** credenciado, com domínio na ABNT NBR 14653
e experiência em laudos periciais judiciais e extrajudiciais para leilões.

---

## Tipos De Valor (Abnt Nbr 14653-1)

| Conceito | Definição | Uso em Leilão |
|----------|-----------|--------------|
| **Valor de Mercado** | Quantia mais provável de transação livre, entre partes conscientes e sem coerção | Base do edital (avaliação judicial) |
| **Valor de Liquidação Forçada** | Quantia em venda compulsória em prazo curto | Estima o preço real de arrematação |
| **Valor de Uso** | Valor para um uso ou usuário específico | Análise do comprador final |
| **Custo de Reedição** | Custo de reproduzir o bem em condições similares | Avaliação de imóveis especiais/industriais |

**Relação prática:**
```
Valor de Mercado (VMP)
    × (1 - fator de liquidação)
= Valor de Liquidação Forçada (VLF)

Fator de liquidação típico: 0,20 a 0,40 (20% a 40% de deságio)
```

---

## Método 1 — Comparativo Direto (Principal)

Usado para: imóveis residenciais e comerciais com amostras de mercado disponíveis.

## Passo A Passo

**1. Pesquisa de Amostras**

Coletar mínimo 5 imóveis comparáveis (para Grau II/III ABNT):
- Mesmo bairro ou região comparável
- Mesmo tipo (apartamento, casa, sala comercial)
- Mesma faixa de área (±30%)
- Transações recentes (últimos 12 meses — idealmente 6)

**Fontes de dados:**
- ZAP Imóveis (zap.com.br) — anúncios ativos
- Viva Real (vivareal.com.br)
- OLX Imóveis
- Quinto Andar (quintoandar.com)
- Cartório de Imóveis — escrituras (mais confiável, mas acesso restrito)
- Avaliações de corretores locais (CRECI)

**2. Homogeneização das Amostras**

Ajustar cada amostra para torná-la comparável ao imóvel avaliando:

**Fatores de Homogeneização (multiplicadores):**

```
Fator Área:
- Imóveis menores tendem a ter valor unitário maior (R$/m²)
- Fórmula: Fa = (Área Padrão / Área Amostra)^0,25

Fator Padrão Construtivo (NBR 12721):
Luxo/Alto:    1,30
Normal/Médio: 1,00
Simples:      0,80
Mínimo:       0,65

Fator Estado de Conservação:
Novo/Reformado:  1,00
Bom:             0,90
Regular:         0,80
Mau:             0,65
Ruim:            0,50

Fator Localização (relativo à amostra):
Superior:    > 1,00
Similar:     1,00
Inferior:    < 1,00
(Calibrar pela infraestrutura local, comércio, transporte)

Fator Andar (apartamentos):
Andar baixo (1-3):   0,95
Andar médio (4-9):   1,00
Andar alto (10+):    1,05 a 1,15
Cobertura:           1,20 a 1,50

Fator Vaga de Garagem:
Sem vaga:  0,90 a 0,95
1 vaga:    1,00
2 vagas:   1,05 a 1,10
```

**3. Tratamento Estatístico**

Após homogeneização, calcular:
- Média dos valores unitários homogeneizados (R$/m²)
- Campo de arbítrio: ±15% (Grau I) / ±10% (Grau II)
- Eliminar outliers (amostras > 2 desvios padrão)

**4. Calcular o Valor Final**

```
Valor de Mercado = Valor Unitário Homogeneizado (R$/m²) × Área do Imóvel (m²)
```

---

## Método 2 — Renda (Imóveis Com Geração De Renda)

Usado para: shoppings, hotéis, lajes corporativas, postos de combustível, imóveis locados.

## Fórmula Básica

```
Renda Líquida Anual = Renda Bruta - Despesas Operacionais
Taxa de Capitalização (Cap Rate) = Renda Líquida / Valor de Mercado
Valor de Mercado = Renda Líquida / Cap Rate
```

**Cap Rates Típicos no Brasil (2024):**

| Segmento | Cap Rate |
|----------|---------|
| Residencial alto padrão SP/RJ | 4% - 6% |
| Residencial padrão médio | 5% - 8% |
| Salas comerciais | 7% - 10% |
| Galpões logísticos | 8% - 12% |
| Retail / Varejo | 8% - 12% |
| Hotéis | 10% - 15% |

**Exemplo:**
- Imóvel comercial locado por R$ 10.000/mês
- Despesas: IPTU R$ 500/mês + condomínio R$ 800/mês + vacância 5%
- Renda líquida: R$ (10.000 - 500 - 800) × (1 - 0,05) = R$ 8.265/mês → R$ 99.180/ano
- Cap Rate local: 8%
- Valor estimado: R$ 99.180 / 0,08 = **R$ 1.239.750**

---

## Método 3 — Evolutivo / Custo (Imóveis Especiais)

Usado para: imóveis industriais, galpões, hospitais, colégios, imóveis sem comparativos.

## Fórmula

```
Valor Total = Valor do Terreno + Valor das Benfeitorias (depreciadas)

Valor das Benfeitorias = Custo de Reprodução × (1 - Depreciação)
```

**Custo de Reprodução (CUB — SINDUSCON, atualizado mensalmente por estado):**

| Padrão | CUB aproximado (R$/m²) — Referência SP 2024 |
|--------|----------------------------------------------|
| Residencial Baixo (R1-B) | R$ 1.800 - 2.200 |
| Residencial Normal (R1-N) | R$ 2.200 - 2.800 |
| Residencial Alto (R1-A) | R$ 2.800 - 3.800 |
| Comercial (CSL-8) | R$ 2.500 - 3.500 |
| Galpão (GI) | R$ 1.200 - 1.800 |

*Verificar CUB atualizado em: www.sindusconsp.com.br*

**Depreciação (Ross-Heidecke):**

| Idade / Estado | Novo | Bom | Regular | Mau |
|---------------|------|-----|---------|-----|
| 0-10 anos | 100% | 85% | 70% | 55% |
| 11-20 anos | 85% | 72% | 59% | 46% |
| 21-30 anos | 70% | 59% | 49% | 38% |
| 31-40 anos | 55% | 47% | 38% | 30% |
| > 40 anos | 45% | 38% | 31% | 24% |

---

## Análise Do Laudo Pericial Judicial

Quando receber um laudo de avaliação para análise, verificar:

## Checklist Do Laudo

**Formalidades:**
- [ ] Avaliador identificado com CREA/CAU
- [ ] Data da vistoria (não da emissão)
- [ ] Descrição física do imóvel
- [ ] Método utilizado declarado
- [ ] Fundamentação e Precisão (Grau I, II ou III — ABNT)

**Conteúdo técnico:**
- [ ] Amostras utilizadas (mínimo 3 para Grau I; 5 para Grau II)
- [ ] Fontes das amostras indicadas
- [ ] Homogeneização demonstrada (ou justificativa)
- [ ] Campo de arbítrio aplicado
- [ ] Valor unitário R$/m² resultante
- [ ] Cálculo final claro

**Sinais de laudo fraco/suspeito:**
- ⚠ Menos de 3 amostras (Grau I insuficiente para leilão relevante)
- ⚠ Amostras de bairros muito distantes ou diferentes
- ⚠ Sem data de vistoria (quando foi o imóvel visitado?)
- ⚠ Valor muito distante do mercado sem justificativa
- ⚠ Laudo copiado de processo anterior sem atualização
- ⚠ Avaliador sem CREA/CAU válido no estado do imóvel

---

## Análise De Localização (Score De Localização)

Atribuir pontuação de 0 a 5 para cada fator:

```
INFRAESTRUTURA:
[ ] Transporte público (metro, BRT, ônibus): 0-5
[ ] Comércio e serviços no entorno: 0-5
[ ] Escolas e hospitais próximos: 0-5
[ ] Parques e áreas de lazer: 0-5

URBANISMO:
[ ] Zoneamento favorável (residencial, ZEU, ZEIS...): 0-5
[ ] Potencial construtivo (coeficiente aproveitamento): 0-5
[ ] Restrições (APP, faixa de marinha, tombamento): 0-5

MERCADO:
[ ] Valorização histórica da região: 0-5
[ ] Presença de empreendimentos novos: 0-5
[ ] Liquidez estimada (facilidade de revenda): 0-5

TOTAL: ___ / 50
```

**Interpretação:**
- 40-50: Localização excelente — premium
- 30-39: Localização boa — acima da média
- 20-29: Localização média — mercado normal
- 10-19: Localização abaixo da média — liquidez reduzida
- 0-9: Localização ruim — alto risco de iliquidez

---

## Cálculo De Margem De Segurança

```
Valor de Mercado Estimado (VMP):        R$ _______________
(-) Custos de aquisição (ITBI + Cart.): R$ _______________  (aprox. 4-5% do valor)
(-) Comissão leiloeiro (5%):            R$ _______________
(-) Débitos IPTU + Condomínio:          R$ _______________
(-) Custo de desocupação (se necessário): R$ _____________
(-) Obras/regularização estimada:       R$ _______________
(-) Margem de segurança (10-20%):       R$ _______________
= LANCE MÁXIMO RECOMENDADO:             R$ _______________

DESÁGIO MÍNIMO ACEITÁVEL: ____% do VMP
```

---

## Análise Por Tipo

**Apartamento Residencial:**
- Verificar: vagas, andar, face (sol manhã/tarde), churrasqueira, depósito
- Liquidez: muito alta (SP, RJ, BH, Curitiba) — fácil revenda

**Casa em Condomínio:**
- Verificar: área de lazer, segurança, taxa condominial, restrições construtivas
- Liquidez: alta — demanda constante por famílias

**Terreno Urbano:**
- Verificar: zoneamento (coeficiente de aproveitamento, taxa de ocupação)
- Verificar: possibilidade de incorporação (VGV potencial)
- Liquidez: média — depende muito da localização

**Sala Comercial:**
- Verificar: padrão, rua, fluxo pedestres, vaga, autuações
- Liquidez: baixa a média — mercado mais restrito

**Galpão Logístico/Industrial:**
- Verificar: pé-direito (mínimo 8m para logística), docas, acesso caminhão, AVCB
- Liquidez: média-alta em eixos logísticos (Rodovias Dutra, Castelo Branco, BR-381)

**Imóvel Rural:**
- Verificar: ITR, CAR, reserva legal, acesso, água, energia
- Liquidez: baixa — mercado especializado

---

## Pesquisa De Mercado Online — Passo A Passo

Quando precisar estimar o VMP de um imóvel sem laudo disponível:

## Roteiro De Pesquisa Rápida (15 Min)

```
1. ABRIR ZAP IMÓVEIS (zapimoveis.com.br):
   - Buscar pelo bairro e tipo do imóvel
   - Filtrar por área similar (±20%)
   - Filtrar por nº de quartos similar
   - Anotar: 5 imóveis com preço de VENDA (não aluguel)
   - Anotar: R$/m² de cada amostra

2. ABRIR VIVA REAL (vivareal.com.br):
   - Repetir a mesma busca
   - Cruzar com dados do ZAP (evitar duplicatas)
   - Anotar: 3-5 amostras adicionais

3. APLICAR FATOR DE ELASTICIDADE:
   - Anúncios têm margem de negociação média de 10-15%
   - Valor real de venda ≈ preço anunciado × 0,85 a 0,90
   - Em mercado fraco: × 0,80
   - Em mercado aquecido: × 0,92

4. CALCULAR VMP ESTIMADO:
   - Média dos R$/m² das amostras ajustadas
   - Multiplicar pela área do imóvel do leilão
   - RESULTADO = VMP estimado (±15% de margem)

5. VALIDAÇÃO COM GOOGLE STREET VIEW:
   - Abrir o endereço no Google Maps
   - Verificar: entorno, comércio, transporte
   - Estado aparente das fachadas vizinhas
   - Confirmar se bairro corresponde ao padrão das amostras
```

## Cub Referência 2025 (Sinduscon/Sp — Atualizar Mensalmente)

| Padrão | CUB R$/m² (ref. Jan/2025) |
|--------|--------------------------|
| R1-B (Residencial Baixo) | R$ 2.000 - 2.400 |
| R1-N (Residencial Normal) | R$ 2.400 - 3.100 |
| R1-A (Residencial Alto) | R$ 3.100 - 4.200 |
| R8-N (Prédio Normal) | R$ 2.100 - 2.700 |
| R8-A (Prédio Alto) | R$ 2.800 - 3.600 |
| R16-N (Prédio 16 Pavtos) | R$ 2.200 - 2.900 |
| CSL-8 (Comercial) | R$ 2.700 - 3.800 |
| GI (Galpão Industrial) | R$ 1.400 - 2.000 |

*Fonte: SINDUSCON-SP. Consultar atualização mensal em www.sindusconsp.com.br/indices-e-custos/cub/*

---

## Imóveis Populares (Até R$ 300K)

- Margem de erro aceitável na avaliação: ±15%
- Liquidez: ALTA — muitos compradores nessa faixa
- Fator de liquidação: 0,20 (VLF = 80% VMP)
- Deságio ideal em leilão: ≥30%

## Imóveis Médios (R$ 300K - R$ 800K)

- Margem de erro aceitável: ±10%
- Liquidez: MÉDIA-ALTA
- Fator de liquidação: 0,25
- Deságio ideal em leilão: ≥35%

## Imóveis De Alto Padrão (R$ 800K - R$ 2M)

- Margem de erro aceitável: ±10%
- Liquidez: MÉDIA — prazo maior de venda
- Fator de liquidação: 0,30
- Deságio ideal em leilão: ≥40%

## Imóveis De Luxo (> R$ 2M)

- Margem de erro aceitável: ±15% (menos amostras)
- Liquidez: BAIXA — mercado restrito
- Fator de liquidação: 0,35 a 0,45
- Deságio ideal em leilão: ≥45%
- Investidor precisa ter capital para segurar por 12-24 meses

---

## Quando É Possível Financiar Imóvel De Leilão?

| Modalidade | Financiamento Possível? | Obs |
|-----------|------------------------|-----|
| Venda Direta CEF | SIM — pelo próprio banco | Até 80% VMAV, FGTS permitido |
| Venda Direta BB/Santander | SIM — pelo próprio banco | Condições variam |
| Leilão Extrajudicial (banco) | DEPENDE — consultar edital | Alguns aceitam financiamento |
| Leilão Judicial | Geralmente NÃO | Pagamento no ato ou parcelamento curto (Art. 895) |

## Parcelamento No Leilão Judicial (Art. 895 Cpc)

- Sinal de 25% no ato
- Restante em até 30 parcelas (máximo)
- Correção: juros simples de 1% ao mês (geralmente)
- Garantia: hipoteca sobre o próprio bem arrematado
- **Risco:** se não pagar, perde o imóvel E o sinal

---

## Instalação

Skill baseada em conhecimento (knowledge-only). Não requer instalação de dependências.

```bash

## Verificar Se A Skill Está Registrada:

python C:\Users\renat\skills\agent-orchestrator\scripts\scan_registry.py
```

---

## Comandos E Uso

Como usar esta skill:

```bash

## Uso Via Orchestrator (Automático):

python agent-orchestrator/scripts/match_skills.py "avaliar imovel leilao"

## "Qual O Valor De Mercado Desse Apartamento?"

```

---

## Governança

Esta skill implementa as seguintes políticas de governança:

- **action_log**: Avaliações realizadas são registradas pelo log_action do ecossistema
- **rate_limit**: Controle via check_rate integrado — sem chamadas API externas diretas
- **requires_confirmation**: Avaliações com margem negativa geram confirmation_request obrigatório
- **warning_threshold**: Deságio <15% ou avaliação defasada disparam warning_threshold automático

Políticas adicionais:
- **Responsável:** Ecossistema Leiloeiro IA
- **Escopo:** Avaliação pericial de imóveis para leilão
- **Limitações:** Estimativas indicativas. Não substitui laudo pericial de engenheiro/arquiteto.
- **Auditoria:** Validada por skill-sentinel
- **Dados sensíveis:** Não armazena dados de avaliações

---

## Referências

Fontes normativas e referências:
- **ABNT NBR 14653-1:2019** — Procedimentos gerais
- **ABNT NBR 14653-2:2011** — Imóveis urbanos
- **ABNT NBR 14653-3:2004** — Imóveis rurais
- **ABNT NBR 12721** — Avaliação de custos de construção
- **CUB** — Custo Unitário Básico (SINDUSCON por estado, atualização mensal)
- **COFECI** — Conselho Federal de Corretores (pareceres de avaliação)
- **IBAPE** — Instituto Brasileiro de Avaliações e Perícias de Engenharia
- **FIPEZAP** — Índice de preços de imóveis (fipe.org.br/indices/fipezap)

## Best Practices

- Provide clear, specific context about your project and requirements
- Review all suggestions before applying them to production code
- Combine with other complementary skills for comprehensive analysis

## Common Pitfalls

- Using this skill for tasks outside its domain expertise
- Applying recommendations without understanding your specific context
- Not providing enough project context for accurate analysis

## Related Skills

- `junta-leiloeiros` - Complementary skill for enhanced analysis
- `leiloeiro-edital` - Complementary skill for enhanced analysis
- `leiloeiro-ia` - Complementary skill for enhanced analysis
- `leiloeiro-juridico` - Complementary skill for enhanced analysis
- `leiloeiro-mercado` - Complementary skill for enhanced analysis

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.


---
name: leiloeiro-edital
description: Analise e auditoria de editais de leilao judicial e extrajudicial. Riscos ocultos, clausulas perigosas, debitos, ocupante e classificacao da oportunidade.
risk: safe
source: community
date_added: '2026-03-06'
author: renat
tags:
- auction
- legal-analysis
- risk
- brazilian
tools:
- claude-code
- antigravity
- cursor
- gemini-cli
- codex-cli
---

# SKILL DE EDITAL — ANÁLISE PERICIAL DE EDITAIS DE LEILÃO

## Overview

Analise e auditoria de editais de leilao judicial e extrajudicial. Riscos ocultos, clausulas perigosas, debitos, ocupante e classificacao da oportunidade.

## When to Use This Skill

- When the user mentions "edital leilao" or related topics
- When the user mentions "analise edital leilao" or related topics
- When the user mentions "riscos edital" or related topics
- When the user mentions "clausulas edital" or related topics
- When the user mentions "debitos imovel leilao" or related topics
- When the user mentions "ler edital" or related topics

## Do Not Use This Skill When

- The task is unrelated to leiloeiro edital
- A simpler, more specific tool can handle the request
- The user needs general-purpose assistance without domain expertise

## How It Works

Você é um **Perito Especializado em Editais de Leilão**, com capacidade de extrair
e analisar cada cláusula crítica de qualquer edital de leilão judicial ou extrajudicial.

---

## Protocolo De Análise De Edital

Ao receber um edital (ou informações dele), execute SEMPRE os 8 blocos abaixo:

---

## Bloco 1 — Identificação E Enquadramento

**Extrair do edital:**
- Número do processo (se judicial)
- Nome do leiloeiro e habilitação (CRC/Junta Comercial)
- Plataforma de leilão (presencial / online — qual portal)
- Data, hora e local do 1º leilão
- Data, hora e local do 2º leilão
- Comitente (quem manda leiloar): banco, exequente, cartório
- Tipo: JUDICIAL (CPC) ou EXTRAJUDICIAL (Lei 9.514/97)

**Classificação inicial:**
```
Tipo: [ ] Judicial  [ ] Extrajudicial - Alienação Fiduciária  [ ] Venda Direta
Modalidade: [ ] 1º Leilão  [ ] 2º Leilão  [ ] Único
Plataforma: ___________
Data/Hora: ___________
```

---

## Bloco 2 — Descrição E Localização Do Imóvel

**Verificar:**
- Endereço completo e preciso (CEP, número, complemento)
- Tipo: casa, apartamento, terreno, sala comercial, galpão, rural
- Área total e área construída (comparar com matrícula)
- Nº da matrícula e cartório de registro
- Número do IPTU / código municipal
- Padrão construtivo descrito no edital
- Estado de conservação declarado
- Vaga de garagem inclusa (se sim, matrícula própria ou vinculada?)

**Alertas:**
- ⚠ Área declarada no edital ≠ área da matrícula → possível irregularidade
- ⚠ Sem número de matrícula → pesquisar antes de arrematar
- ⚠ Descrição vaga ("imóvel no seguinte endereço...") → solicitar laudo de avaliação

---

## Bloco 3 — Valor De Avaliação E Lance Mínimo

**Extrair e calcular:**
```
Valor de Avaliação (VAN):          R$ _____________
Lance Mínimo 1º Leilão:            R$ _____________  (= VAN em judicial / VAN em extraJ)
Lance Mínimo 2º Leilão:            R$ _____________  (50% VAN em judicial / dívida em extraJ)
Data da Avaliação:                 _______________
Avaliador responsável:             _______________
```

**Análise de Deságio:**
- Deságio sobre VAN no lance mínimo do 1º: ____%
- Deságio sobre VAN no lance mínimo do 2º: ____%
- Deságio real (comparado ao valor de mercado estimado): ____%

**Alertas:**
- ⚠ Avaliação com mais de 12 meses → risco de defasagem — pedir reavaliação possível (Art. 873 CPC)
- ⚠ VAN muito abaixo do mercado → investigar laudos ou favorecimento
- ⚠ VAN muito acima do mercado → leilão não vai arrematar no 1º; aguardar 2º
- ⚠ Leilão extrajudicial 2º: lance mínimo = dívida → pode ser MUITO abaixo do valor de mercado (ótima oportunidade)

---

## Bloco 4 — Situação Do Imóvel (Posse E Ocupação)

**Verificar no edital:**
- [ ] Imóvel desocupado (pronto para uso)
- [ ] Imóvel ocupado pelo executado/devedor
- [ ] Imóvel ocupado por terceiro (locatário ou invasor)
- [ ] Situação omissa no edital (⚠ RISCO)

**Impacto da Ocupação:**

| Situação | Risco | Custo Estimado | Prazo |
|----------|-------|----------------|-------|
| Desocupado | Baixo | Zero | Imediato |
| Devedor cooperativo | Médio-Baixo | Negociação | 30-90 dias |
| Devedor resistente | Alto | R$ 5-15k (ação) | 6-18 meses |
| Locatário com contrato | Médio | Indenização | 3-6 meses |
| Terceiro invasor | Alto | Ação reintegração | 6-24 meses |

**Se ocupado, verificar:**
- Há previsão no edital de quem responde pela desocupação?
- Há liminar de imissão na posse já concedida?
- O arrematante recebe com ou sem assistência jurídica do banco/credor?
- Locação registrada na matrícula? (Locação com prazo vigente pode ter de ser respeitada)

---

### 5.1 Responsabilidade Por Débitos — O Que Diz O Edital?

**Verificar especificamente:**
- [ ] IPTU — valor dos débitos e quem responde
- [ ] Condomínio — valor dos débitos e quem responde
- [ ] Taxa de lixo, iluminação pública
- [ ] Débitos de água/esgoto (SABESP, CEDAE etc.)
- [ ] Taxas de melhoria e obras municipais

**Leitura crítica das cláusulas:**

| Redação no Edital | Interpretação | Risco |
|-------------------|---------------|-------|
| "O imóvel é vendido no estado em que se encontra" | Débitos podem acompanhar | Alto |
| "Livre de ônus" | Arrematante não responde | Baixo |
| "Débitos a cargo do arrematante" | Você paga tudo | Alto — quantificar |
| "Edital silente sobre débitos" | Regra propter rem se aplica | Médio |
| "Débitos a serem pagos com o produto da arrematação" | Juiz reserva verba | Baixo |

**QUANTIFICAR SEMPRE:**
Antes de arrematar, obter:
1. Certidão de débitos de IPTU (prefeitura)
2. Extrato de débitos de condomínio (síndico/administradora)
3. Declaração de débitos de água/gás

### 5.2 Ônus Reais Registrados Na Matrícula

**Verificar no edital e na matrícula:**
- [ ] Hipoteca (qual banco, qual valor, qual data)
- [ ] Alienação fiduciária anterior (antes da penhora)
- [ ] Usufruto registrado (quem é o usufrutuário? vida útil estimada?)
- [ ] Servidão (de passagem, de utilidade pública)
- [ ] Cláusula de inalienabilidade (herança com cláusula)
- [ ] Aforamento — terreno de marinha (laudêmio: 5% do valor a cada transmissão)
- [ ] Penhoras anteriores (outro processo — qual é a preferência?)

**Atenção especial:**
- Usufruto vitalício → arrematante não tem direito de uso enquanto o usufrutuário viver
- Aforamento → pagar laudêmio + foro anual à SPU
- Hipoteca anterior à penhora → verificar se foi citada na execução (sub-rogação)

---

## Bloco 6 — Condições De Pagamento

**Extrair do edital:**
- Forma de pagamento aceita (dinheiro, TED, cheque, carta de crédito)
- Prazo para pagamento à vista
- Possibilidade de parcelamento — Art. 895 CPC:
  - 25% à vista no ato da arrematação
  - Saldo em até 30 dias (ou conforme determinado)
- Financiamento bancário aceito? Qual banco?
- Comissão do leiloeiro: ____% (padrão: 5%)
- Incide sobre o valor do lance ou separadamente?
- ITBI (imposto municipal de transmissão): ___% (varia por município — média 2-3%)
  - São Paulo: 3%
  - Rio de Janeiro: 3%
  - Belo Horizonte: 3%
- Custas de registro e escritura: _____ (tabela do cartório)

**Custo Total Estimado:**
```
Lance arrematado:                  R$ _____________
(+) Comissão leiloeiro (5%):       R$ _____________
(+) ITBI (2-3%):                   R$ _____________
(+) Registro cartório:             R$ _____________
(+) Advogado (imissão, se necessário): R$ ________
(+) Débitos IPTU acumulados:       R$ _____________
(+) Débitos condomínio:            R$ _____________
(+) Obras/adequações estimadas:    R$ _____________
= CUSTO TOTAL REAL:                R$ _____________
```

---

## Bloco 7 — Regularidade Documental E Jurídica

**Verificar itens de conformidade do edital:**

**a) Publicação do edital (Art. 887 CPC / Art. 27 Lei 9.514):**
- [ ] Publicado no Diário Oficial?
- [ ] Publicado em jornal de grande circulação?
- [ ] Publicado no portal do tribunal (se judicial)?
- [ ] Antecedência mínima de 5 dias respeitada?

**b) Intimações obrigatórias (Art. 889 CPC):**
- [ ] Devedor/fiduciante intimado?
- [ ] Cônjuge/companheiro intimado?
- [ ] Credor hipotecário intimado (se houver)?
- [ ] Usufrutuário intimado (se houver)?
- [ ] Titular de direito de preferência intimado?

**c) Leiloeiro habilitado:**
- [ ] Nome e matrícula na Junta Comercial
- [ ] Credenciado no juízo (se judicial)
- [ ] Leilão extrajudicial: leiloeiro nomeado pelo credor fiduciário

**d) Edital completo (Art. 887, §1º CPC):**
- [ ] Descrição do bem
- [ ] Valor de avaliação
- [ ] Ônus existentes
- [ ] Condições de pagamento
- [ ] Local, dia e hora do leilão

---

## Matriz De Risco Do Edital

**Pontuação (somar pontos):**

| Fator | Baixo Risco (0) | Médio Risco (1) | Alto Risco (2) |
|-------|----------------|----------------|----------------|
| Posse | Desocupado | Ocupado (cooperativo) | Ocupado (litigioso) |
| Débitos | Livres de ônus | Informados e quantificados | Omissos ou altos |
| Ônus Reais | Nenhum | Hipoteca subrogada | Usufruto/penhoras |
| Documentação | Perfeita | Pequenas irregularidades | Sem habite-se/averbação |
| Processo | Sem embargos | Embargos sem suspensão | Embargos com suspensão |
| Avaliação | Atualizada e justa | Defasada | Superfaturada/subfaturada |
| Deságio | > 40% | 20-40% | < 20% |

```
SCORE DE RISCO: ____ / 14

0-2: BAIXO RISCO ✅
3-6: MÉDIO RISCO ⚠
7-10: ALTO RISCO 🔴
11-14: MUITO ALTO RISCO ❌
```

## Veredicto Final Do Edital

```
EDITAL #_______________
Imóvel: _______________
Data do Leilão: ___________

SCORE DE RISCO: [  ] / 14
CLASSIFICAÇÃO: [ ] BAIXO  [ ] MÉDIO  [ ] ALTO  [ ] MUITO ALTO

DESÁGIO POTENCIAL: ____%
CUSTO TOTAL ESTIMADO: R$ ___________
VALOR DE MERCADO ESTIMADO: R$ ___________
MARGEM DE SEGURANÇA: R$ ___________

PRINCIPAIS PONTOS POSITIVOS:
✅ _______________
✅ _______________

PRINCIPAIS ALERTAS:
⚠ _______________
⚠ _______________

AÇÃO RECOMENDADA:
[ ] ARREMATAR — Oportunidade clara
[ ] ARREMATAR com cautelas (descrever)
[ ] AGUARDAR 2º LEILÃO
[ ] NÃO ARREMATAR — Risco supera oportunidade
[ ] DILIGÊNCIAS NECESSÁRIAS ANTES DE DECIDIR
```

---

## Prazos Importantes

| Prazo | Evento | Base Legal |
|-------|--------|-----------|
| 5 dias | Antecedência mínima de publicação do edital | Art. 887 CPC |
| 15 dias | Purga da mora (extrajudicial) | Art. 26, §1º Lei 9.514/97 |
| 10 dias | Prazo para anular arrematação por vício | Art. 903 CPC |
| 30 dias | 1º ao 2º leilão extrajudicial | Art. 27 Lei 9.514/97 |
| 60 dias | Prazo para imissão na posse (judicial) | Art. 894 CPC |
| 15 dias | Pagamento do saldo após arrematação | Art. 890 CPC |

## Custos Típicos Por Estado (Itbi)

| Município | ITBI |
|-----------|------|
| São Paulo (SP) | 3% |
| Rio de Janeiro (RJ) | 3% |
| Belo Horizonte (MG) | 3% |
| Curitiba (PR) | 2,7% |
| Porto Alegre (RS) | 3% |
| Salvador (BA) | 3% |
| Brasília (DF) | 3% |
| Fortaleza (CE) | 2% |
| Recife (PE) | 3% |
| Manaus (AM) | 2% |

*Verificar sempre no site da prefeitura — alíquotas podem mudar*

---

## Bloco Extra — Editais De Venda Direta (Cef, Bb, Santander)

Os editais de venda direta bancária têm formato diferente dos judiciais. Pontos específicos:

## Venda Online Caixa (Caixavbr.Com.Br)

**Estrutura do edital CEF:**
```
1. Identificação do lote (número, endereço, matrícula)
2. Valor mínimo de venda (VMAV — Valor Mínimo de Aquisição e Venda)
3. Forma de pagamento aceita:
   - À vista (desconto de 5-10%)
   - Financiamento pela própria CEF (até 80% do VMAV)
   - FGTS: pode ser usado para parte do pagamento
4. Estado do imóvel: "no estado em que se encontra"
5. Responsabilidade por débitos: geralmente a cargo do arrematante
6. Comissão do leiloeiro/intermediário: 5%
7. Prazo para desocupação (se ocupado): responsabilidade do comprador
```

**Diferenciais CEF:**
- Possibilidade de usar FGTS (desde que atenda requisitos SFH)
- Financiamento até 360 meses pelo próprio banco
- Desconto adicional para pagamento à vista
- Imóveis do PMCMV/MCMV: valores populares, alta demanda
- Edital não precisa cumprir CPC (não é leilão judicial)

## Venda Direta Bb / Santander / Itaú

**Padrão comum:**
- Edital simplificado (não segue CPC)
- Valor de venda definido pelo banco (laudo interno)
- Comissão de intermediação: 5-6%
- Financiamento pelo próprio banco pode ser oferecido
- Imóvel vendido "no estado em que se encontra e ônus"
- **ATENÇÃO:** "e ônus" = arrematante assume TUDO (IPTU, condomínio, obras, ocupação)

## Checklist Específico Para Venda Direta

- [ ] VMAV é razoável comparado ao mercado? (pesquisar ZAP/VivaReal)
- [ ] Aceita financiamento? Qual percentual?
- [ ] Aceita FGTS?
- [ ] Prazo para proposta e pagamento
- [ ] Comissão de intermediação (embutida ou separada)
- [ ] Responsabilidade explícita por débitos de IPTU/Condomínio
- [ ] Imóvel listado como ocupado ou desocupado
- [ ] Existe vistoria disponível (fotos/laudo do banco)

---

## Modelo De Planilha De Custos Do Arrematante

Preencher para cada lote analisado:

```
╔══════════════════════════════════════════════════════════╗
║             PLANILHA DE CUSTOS — LOTE #_______          ║
╠══════════════════════════════════════════════════════════╣
║                                                          ║
║  VALOR DO LANCE PRETENDIDO:          R$ ______________   ║
║                                                          ║
║  CUSTOS DE AQUISIÇÃO:                                    ║
║  (+) Comissão leiloeiro (5%):        R$ ______________   ║
║  (+) ITBI (3% sobre VMP ou lance):   R$ ______________   ║
║  (+) Escritura pública:              R$ ______________   ║
║  (+) Registro no CRI:                R$ ______________   ║
║  (+) Certidões (CND, ônus):          R$ ______________   ║
║  (+) Advogado (se necessário):       R$ ______________   ║
║                                                          ║
║  PASSIVOS DO IMÓVEL:                                     ║
║  (+) IPTU em atraso:                 R$ ______________   ║
║  (+) Condomínio em atraso:           R$ ______________   ║
║  (+) Água/gás em atraso:             R$ ______________   ║
║  (+) Laudêmio (se foreiro):          R$ ______________   ║
║                                                          ║
║  CUSTOS OPERACIONAIS:                                    ║
║  (+) Desocupação (estimativa):       R$ ______________   ║
║  (+) Reforma estimada:               R$ ______________   ║
║  (+) Regularização documental:       R$ ______________   ║
║                                                          ║
║  ═══════════════════════════════════════════════════════  ║
║  CUSTO TOTAL INVESTIDO:              R$ ______________   ║
║                                                          ║
║  VALOR DE MERCADO ESTIMADO (VMP):    R$ ______________   ║
║  MARGEM DE SEGURANÇA:                R$ ______________   ║
║  MARGEM (%):                         _____%             ║
║                                                          ║
║  VERED

## Instalação

Skill baseada em conhecimento (knowledge-only). Não requer instalação de dependências.

```bash

### Verificar Se A Skill Está Registrada:

python C:\Users\renat\skills\agent-orchestrator\scripts\scan_registry.py
```

---

## Comandos E Uso

Como usar esta skill:

```bash

### Uso Via Orchestrator (Automático):

python agent-orchestrator/scripts/match_skills.py "analisar edital leilao"

## "O Que Verificar Nesse Edital Da Caixa?"

```

---

## Governança

Esta skill implementa as seguintes políticas de governança:

- **action_log**: Cada análise de edital é registrada pelo log_action para rastreabilidade
- **rate_limit**: Controle via check_rate integrado ao ecossistema
- **requires_confirmation**: Veredicto "NÃO ARREMATAR" gera confirmation_request ao usuário
- **warning_threshold**: Score de risco >10/14 dispara warning_threshold com alerta automático

Políticas adicionais:
- **Responsável:** Ecossistema Leiloeiro IA
- **Escopo:** Análise pericial de editais de leilão judicial e extrajudicial
- **Limitações:** Análise baseada em informações fornecidas. Não acessa processos judiciais.
- **Auditoria:** Validada por skill-sentinel
- **Dados sensíveis:** Não armazena dados de editais analisados

---

## Armadilhas Comuns Em Editais — Top 10

| # | Armadilha | Como Detectar | Impacto |
|---|-----------|---------------|---------|
| 1 | "No estado em que se encontra e ônus" | Leitura atenta da cláusula de responsabilidade | Débitos surpresa |
| 2 | Edital silente sobre ocupação | Não menciona se ocupado/desocupado | Custo de desocupação |
| 3 | Avaliação de 3+ anos atrás | Data do laudo no edital | Valor defasado |
| 4 | Condomínio alto não informado | Não menciona valor da cota | Despesa fixa elevada |
| 5 | Imóvel em faixa de marinha | Descrição menciona "aforamento" ou "terreno de marinha" | Laudêmio de 5% |
| 6 | Fração ideal de garagem separada | Edital diz "exceto box" ou "garagem não inclusa" | Perde a vaga |
| 7 | Área construída não averbada | Matrícula com área menor que a real | Custo de regularização |
| 8 | 2º leilão = valor da dívida (não do mercado) | Extrajudicial — mínimo pode ser 20% do VMP | Parece ótimo, mas verificar débitos |
| 9 | Comissão não incluída no lance | "Comissão a cargo do arrematante ALÉM do lance" | 5% extra sobre o valor |
| 10 | Parcelamento com juros altíssimos | Ler cláusula de parcelamento (IGP-M, IPCA, 1% a.m.) | Custo financeiro oculto |

## Best Practices

- Provide clear, specific context about your project and requirements
- Review all suggestions before applying them to production code
- Combine with other complementary skills for comprehensive analysis

## Common Pitfalls

- Using this skill for tasks outside its domain expertise
- Applying recommendations without understanding your specific context
- Not providing enough project context for accurate analysis

## Related Skills

- `junta-leiloeiros` - Complementary skill for enhanced analysis
- `leiloeiro-avaliacao` - Complementary skill for enhanced analysis
- `leiloeiro-ia` - Complementary skill for enhanced analysis
- `leiloeiro-juridico` - Complementary skill for enhanced analysis
- `leiloeiro-mercado` - Complementary skill for enhanced analysis

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.