Skip to content
Back to skills

Danthamanvoiss Salesportl Landscaping Context Intake

ASecurity

Collect nuanced landscaping and lawn care services context across business model, micro-niche, and operating constraints.

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

Works with

  • cli
  • api

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-landscaping-context-intake --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Danthamanvoiss Salesportl Landscaping Context Intake?

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

Security grade badge for Danthamanvoiss Salesportl Landscaping Context Intake
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jiayaoqijia-danthamanvoiss-salesportl-landscaping-context-inta/badge)](https://www.skillsdirectory.com/skills/jiayaoqijia-danthamanvoiss-salesportl-landscaping-context-inta)

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-landscaping-context-intake
description: Collect nuanced landscaping and lawn care services context across business model, micro-niche, and operating constraints.
version: 2.0.0
tags: [salesportl, landscaping, niche-suite, context-loop, qa-recursive, tool-node-aware]
---

## Purpose
Collect nuanced landscaping and lawn care services context across business model, micro-niche, and operating constraints.

## Use when
- You are operating inside `SalesPortl-Landscaping-Skills-Suite`.
- You need landscaping and lawn care services execution quality for landscaping firms, lawn-care teams, and outdoor service brands.
- You want repeatable, improving workflows that learn from each run via context + memory updates.

## Industry fit: micro-niche variants
- maintenance lawn care
- design/build landscaping
- commercial grounds contracts

## Standard operating patterns (SOP)
- bid and scope standardization
- crew scheduling and route planning
- seasonal upsell cadence

## SalesPortl platform tooling focus (if available in workspace)
- campaigns for seasonal demand and upsells
- click tracking by project type
- workflow nodes for estimate→crew scheduling

## 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. Collect and normalize business goals, constraints, and current maturity level.
2. Identify micro-niche archetype and operational model from the provided variant list.
3. Capture existing stack usage for campaigns, workflows, pipeline, calendar, and web/app assets.
4. List missing context required for reliable execution and propose smallest follow-up questions.

## 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
- Context snapshot: ...
- Micro-niche classification: ...
- Knowns/unknowns and risk flags: ...
- Minimal clarifying question set: ...
```

## 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.md3 KB
  • SOURCE.md488 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…