Skip to content
Back to skills

Danthamanvoiss Salesportl Real Estate Skill Handoff Protocol

ASecurity

Standardize inter-skill handoffs for real estate services work with clear assumptions, approvals, and next-node instructions.

  • 78 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
businessnode

Works with

  • cli

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add jiayaoqijia/cryptoskill --skill danthamanvoiss-salesportl-real-estate-skill-handoff-protocol --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Danthamanvoiss Salesportl Real Estate Skill Handoff Protocol?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Danthamanvoiss Salesportl Real Estate Skill Handoff Protocol
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jiayaoqijia-danthamanvoiss-salesportl-real-estate-skill-handof/badge)](https://www.skillsdirectory.com/skills/jiayaoqijia-danthamanvoiss-salesportl-real-estate-skill-handof)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: salesportl-real-estate-skill-handoff-protocol
description: Standardize inter-skill handoffs for real estate services work with clear assumptions, approvals, and next-node instructions.
version: 2.0.0
tags: [salesportl, real-estate, niche-suite, context-loop, qa-recursive, tool-node-aware]
---

## Purpose
Standardize inter-skill handoffs for real estate services work with clear assumptions, approvals, and next-node instructions.

## Use when
- You are operating inside `SalesPortl-Real-Estate-Skills-Suite`.
- You need real estate services execution quality for real estate teams, brokerages, and property operators.
- You want repeatable, improving workflows that learn from each run via context + memory updates.

## Industry fit: micro-niche variants
- buyer-side teams
- listing-heavy teams
- investor/property management operators

## Standard operating patterns (SOP)
- lead routing by intent/timeline
- listing launch cadence
- showing/offer follow-up workflows

## SalesPortl platform tooling focus (if available in workspace)
- listing campaign node orchestration
- click tracking by listing CTA
- pipeline and calendar automations for showing-to-close

## Required inputs
- Business objective and requested deliverable
- Current context quality (none/partial/verified)
- Business model, offer mix, and target customer profile
- Authority boundary for external actions (draft-only unless approved)
- Available SalesPortl platform features in this workspace

## Workflow
1. Package source objective, context source, assumptions, approvals, and constraints.
2. Include logic checks performed, confidence score, and unresolved risks.
3. Specify downstream skill and exact output format expected.
4. Prevent rework by summarizing completed workflow nodes and generated assets.

## Platform execution checklist
- Campaign orchestration nodes
- Click-tracking and attribution configuration
- Workflow/automation nodes
- Custom agent launch and role-specialized sub-agents
- CRM pipeline and lead stage automation
- Calendar, booking, and follow-up automations
- Website/page/app builder flows (where available)

## Output format
```text
- Handoff packet: ...
- Logic/consistency checks completed: ...
- Risks/open questions: ...
- Exact downstream instructions: ...
```

## Confidence scoring rubric (0-5 each)
- Logic integrity
- Consistency with context and previous decisions
- Thoroughness of analysis
- Completeness for implementation
- Platform/tooling readiness
- Niche-specific relevance
- **Target**: average >= 4.2 before final handoff

## Quality checks
- Output explicitly reflects this industry plus at least one micro-niche variant.
- Recommendations map to practical SalesPortl feature usage when requested.
- Ambiguities are handled by questions, not assumptions.
- Logic is coherent end-to-end across routing, execution, and QA.
- Completeness is verified before finalization; partial output is labeled as partial.

Files in this skill

  • LICENSE1 KB
  • SKILL.md2.9 KB
  • SOURCE.md496 B
  • TRUST.auto.yaml2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…