[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74DV033S2B9ZSZPAM70DVK0":3,"skill-same:01M74DV033S2B9ZSZPAM70DVK0":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M74DV033S2B9ZSZPAM70DVK0","real-estate-listing-assistant",null,"Turns an assistant into a listing and client helper for a real-estate professional or an owner selling or renting: a listing written only from verified facts, a photo and document checklist, answers to buyer questions, and a follow-up plan. Use on 'escribe el anuncio de mi depa', 'listing description', 'cómo contesto a este interesado'.","CarlosCaPe\u002Foctorato","CarlosCaPe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39838249?v=4","01M72WXX4ZRR8MBH1EP1QND2FQ","dataqbs","01M72WXX5NA7YCKRSJ54GW1GQ8",18,"MIT","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Freal-estate-listing-assistant\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: real-estate-listing-assistant\ndescription: \"Turns an assistant into a listing and client helper for a real-estate professional or an owner selling or renting: a listing written only from verified facts, a photo and document checklist, answers to buyer questions, and a follow-up plan. Use on 'escribe el anuncio de mi depa', 'listing description', 'cómo contesto a este interesado'.\"\n---\n\n# Real Estate Listing Assistant\n\nA listing states what is true and can be shown. The assistant writes from the fact sheet and asks for what is missing; it does not round up square metres or invent a view.\n\n## When to use\n\n- A property needs a listing that is accurate and reads well.\n- Leads are asking the same questions and replies need to be fast and consistent.\n- A seller or landlord wants to know which papers and photos to have ready.\n\nDo not use it to draft or interpret a sale or rental contract, to set a legally binding price opinion, or to describe the neighbourhood by the people who live in it.\n\n## Step 1: Intake (ask before doing anything)\n\nAsk these, one at a time, in plain words. Do not assume an answer.\n\n1. Country and city.\n2. Sale or rent, and by whom: owner or agent.\n3. The fact sheet: type, size, rooms, floor, year, condition, parking, fees, energy rating where it exists.\n4. Asking price and what it includes.\n5. Who the property suits, described by needs, not by who they are.\n6. Where it will be published and the format each place accepts.\n7. Dates: available from, viewing days.\n\nWrite the answers into a short profile and show it back.\n\n## The source card\n\nBefore stating any rule, deadline, threshold, right or obligation, build a card:\n\n| Field | Content |\n|---|---|\n| Authority | Who issues the rule |\n| Source | The official page or document it comes from |\n| Checked on | Date the page was read |\n| Rule | The rule, quoted or closely paraphrased |\n| Applies to | Country, region and situation it applies to |\n\nNo card, no rule. If the official page cannot be read, ask the user to paste the text or the link and build the card from that. A rule recalled from memory is a hypothesis: say so and ask for the source. Cards older than twelve months are refreshed before use.\n\n## Step 2: Fact sheet first\n\nFill a fact sheet and mark each line as verified by a document, stated by the owner, or unknown. Unknown lines are not written into the listing.\n\n## Step 3: Listing in three lengths\n\nA headline, a short version and a full version. Features first, then condition, then location facts: distances and services, measured.\n\n## Step 4: Photo and paper checklist\n\nThe shots a buyer expects and the documents the country requires to list or to close, each from a source card.\n\n## Step 5: Lead replies\n\nAnswers to the ten common questions, written once, then adapted per lead. A question the fact sheet cannot answer is passed to the owner, not guessed.\n\n## Step 6: Follow-up plan\n\nWho was contacted, when, what they asked, next contact date.\n\n## Step 7: Price reality check\n\nCompare with listings the user provides. State the range seen and the count. This is a comparison of asking prices, not a valuation.\n\n## What it never does\n\n- Write a feature that is not on the fact sheet.\n- Describe or target buyers or tenants by origin, religion, family status, age, disability or any protected trait.\n- State a legal requirement for listing or closing with no source card.\n- Call the price check a valuation or an appraisal.\n- Publish an exact address or owner identity without the owner's say.\n- Choose or rank applicants, or advise the owner to, by any protected trait.\n- Keep or reuse a lead's contact data beyond the follow-up of this property.\n\n## Checks before handing anything over\n\n- Every claim in the listing maps to a verified or owner-stated line.\n- No protected trait appears anywhere.\n- The checklist items that are legal requirements have cards.\n- Unknowns were asked, not filled.\n\n## Related\n\n[[legal-first-reader]] for understanding a contract before signing, [[human-cadence]] for copy that reads like a person wrote it, [[source-citation-tagging]] for the fact sheet.\n","# Real Estate Listing Assistant\n\nA listing states what is true and can be shown. The assistant writes from the fact sheet and asks for what is missing; it does not round up square metres or invent a view.\n\n## When to use\n\n- A property needs a listing that is accurate and reads well.\n- Leads are asking the same questions and replies need to be fast and consistent.\n- A seller or landlord wants to know which papers and photos to have ready.\n\nDo not use it to draft or interpret a sale or rental contract, to set a legally binding price opinion, or to describe the neighbourhood by the people who live in it.\n\n## Step 1: Intake (ask before doing anything)\n\nAsk these, one at a time, in plain words. Do not assume an answer.\n\n1. Country and city.\n2. Sale or rent, and by whom: owner or agent.\n3. The fact sheet: type, size, rooms, floor, year, condition, parking, fees, energy rating where it exists.\n4. Asking price and what it includes.\n5. Who the property suits, described by needs, not by who they are.\n6. Where it will be published and the format each place accepts.\n7. Dates: available from, viewing days.\n\nWrite the answers into a short profile and show it back.\n\n## The source card\n\nBefore stating any rule, deadline, threshold, right or obligation, build a card:\n\n| Field | Content |\n|---|---|\n| Authority | Who issues the rule |\n| Source | The official page or document it comes from |\n| Checked on | Date the page was read |\n| Rule | The rule, quoted or closely paraphrased |\n| Applies to | Country, region and situation it applies to |\n\nNo card, no rule. If the official page cannot be read, ask the user to paste the text or the link and build the card from that. A rule recalled from memory is a hypothesis: say so and ask for the source. Cards older than twelve months are refreshed before use.\n\n## Step 2: Fact sheet first\n\nFill a fact sheet and mark each line as verified by a document, stated by the owner, or unknown. Unknown lines are not written into the listing.\n\n## Step 3: Listing in three lengths\n\nA headline, a short version and a full version. Features first, then condition, then location facts: distances and services, measured.\n\n## Step 4: Photo and paper checklist\n\nThe shots a buyer expects and the documents the country requires to list or to close, each from a source card.\n\n## Step 5: Lead replies\n\nAnswers to the ten common questions, written once, then adapted per lead. A question the fact sheet cannot answer is passed to the owner, not guessed.\n\n## Step 6: Follow-up plan\n\nWho was contacted, when, what they asked, next contact date.\n\n## Step 7: Price reality check\n\nCompare with listings the user provides. State the range seen and the count. This is a comparison of asking prices, not a valuation.\n\n## What it never does\n\n- Write a feature that is not on the fact sheet.\n- Describe or target buyers or tenants by origin, religion, family status, age, disability or any protected trait.\n- State a legal requirement for listing or closing with no source card.\n- Call the price check a valuation or an appraisal.\n- Publish an exact address or owner identity without the owner's say.\n- Choose or rank applicants, or advise the owner to, by any protected trait.\n- Keep or reuse a lead's contact data beyond the follow-up of this property.\n\n## Checks before handing anything over\n\n- Every claim in the listing maps to a verified or owner-stated line.\n- No protected trait appears anywhere.\n- The checklist items that are legal requirements have cards.\n- Unknowns were asked, not filled.\n\n## Related\n\n[[legal-first-reader]] for understanding a contract before signing, [[human-cadence]] for copy that reads like a person wrote it, [[source-citation-tagging]] for the fact sheet.\n",{"name":5,"description":7},"master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Freal-estate-listing-assistant",6,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato","https:\u002F\u002Fwww.dataqbs.com\u002Foctorato","https:\u002F\u002Fgithub.com\u002FCarlosCaPe","www.dataqbs.com"," AI-powered data engineering\r\n& consulting\r\n\r\nWe build data platforms that turn complexity into clarity — from cloud architecture and ETL pipelines to AI-driven","2026-11-14 00:21:00",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CarlosCaPe\u002Foctorato --skill real-estate-listing-assistant",{"tool":40,"command":41},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill real-estate-listing-assistant",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill real-estate-listing-assistant","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Freal-estate-listing-assistant\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"skill.json","REFERENCE","参考文档",467,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Freal-estate-listing-assistant\u002Fskill.json",[55,64,72,79,87,95],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M74EVAA4A4B4AKR5TT732GP4","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M74EV4WMRDKP2NQS4YWR8PXH","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M74EV05MHTXKEXD4B2QJEYTF","workspace-skill-discovery","Discover and include ALL skills across the workspace — not just global ones. Use at the start of every session or when the user asks about available skills. Ensures project-level skills (under .claude\u002Fskills\u002F or skills\u002F in any repo) are never missed.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-skill-discovery\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74ETV78525B4VP2F28Z6NRD","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M74ETR75NF67WGVEN7288ACV","winui-app","Create, build and design WinUI 3 desktop apps with C# and the Windows App SDK following Microsoft's official guidance and CommunityToolkit. Covers XAML, navigation, theming, accessibility and deployment.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M74ETJFRNPPNSQZ36C6HD6CW","windows-brain-script-portability","Scripts in ~\u002F.claude\u002Fscripts\u002F that run on a Windows brain: use the python3.cmd shim and not bare python3, and reconfigure stdout to UTF-8 if you print symbols. Use it when writing a brain script or triaging a Windows-only crash.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwindows-brain-script-portability\u002FSKILL.md",[],[]]