notice-of-entry
Drafts contract-compliant Notice of Property Entry letters that satisfy Access Agreement advance-notice, scope, and delivery requirements. Trigger when the user mentions notice of entry, right-of-entry notice, property entry notice, access agreement notice, property inspection notification, business-day calendar calculations for entry, COI delivery before property access, or documenting scope/personnel for a real property inspection, environmental assessment, or construction access.
Best use case
notice-of-entry is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Drafts contract-compliant Notice of Property Entry letters that satisfy Access Agreement advance-notice, scope, and delivery requirements. Trigger when the user mentions notice of entry, right-of-entry notice, property entry notice, access agreement notice, property inspection notification, business-day calendar calculations for entry, COI delivery before property access, or documenting scope/personnel for a real property inspection, environmental assessment, or construction access.
Teams using notice-of-entry should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/notice-of-entry/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How notice-of-entry Compares
| Feature / Agent | notice-of-entry | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Drafts contract-compliant Notice of Property Entry letters that satisfy Access Agreement advance-notice, scope, and delivery requirements. Trigger when the user mentions notice of entry, right-of-entry notice, property entry notice, access agreement notice, property inspection notification, business-day calendar calculations for entry, COI delivery before property access, or documenting scope/personnel for a real property inspection, environmental assessment, or construction access.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Notice of Property Entry Produces a notice that satisfies contractual advance-notice provisions, defines scope and personnel, confirms insurance compliance, and creates a defensible evidentiary record so the entry cannot be challenged as unauthorized. **ATTORNEY REVIEW REQUIRED** — No notice produced by this skill may be sent without attorney review. ## Quick Start 1. Gather Agreement details and entry plan (Checkpoint A) 2. Parse notice clause into drafting constraints 3. Verify scope, build entry window, list entrants/equipment, confirm insurance 4. Assemble notice using template 5. Adversarial-proof and finalize 6. Run post-draft alignment (Checkpoint B) and quality audit ## Checkpoint A: Pre-Draft Intake Gather before drafting (apply labeled defaults if user says "use defaults" or "just draft": standard format, 48-hour advance notice, business-day calculation, formal delivery with proof of service): | # | Input | Details | |---|---|---| | 1 | **Parties** | Legal names as in Agreement; recipient addresses/emails per notice clause | | 2 | **Property ID** | Street address, APN/parcel if in Agreement | | 3 | **Entry window** | Date, time, duration, alternatives if permitted; time zone | | 4 | **Purpose/scope** | Activities using the Agreement's own terms | | 5 | **Access areas** | Specific zones tied to exhibits or site plans | | 6 | **Entrants** | Names, roles, affiliations; badge/vehicle info if required | | 7 | **Equipment** | All equipment/vehicles; flag disruptive activities | | 8 | **Insurance** | Policy types, limits, dates, additional insured, endorsements | | 9 | **Safety** | Escort, PPE, pre-entry meetings, sign-in procedures | | 10 | **Delivery method** | Transmission method, timing, proof of service plan | Do NOT guess contractual terms — pause and ask if anything is missing. ## Core Workflow ### Step 1: Parse Notice Clause - Extract minimum lead time, business-day rules, permitted hours, content requirements, delivery methods, prerequisites (e.g., COI before entry) - Determine if lead time is hours, business hours, or business days; whether weekends/holidays count - Determine if notice is effective on sending or receipt — controls last permissible sending time - **Calendar trap**: Friday notice for Monday entry likely violates a two-business-day requirement - Address to exact recipient, address, and email in the Agreement ### Step 2: Verify Scope Against Agreement - Confirm every activity falls within permitted purposes; **flag for attorney review** if arguably outside scope - Use "specific to general" approach: - Specific: "drilling of three 2-inch diameter soil borings to a depth of 10 feet" - Catch-all: "and other activities reasonably related to the Phase II ESA as authorized under Section [__]" - Use the Agreement's own nouns/verbs; reference exhibits and site plans - Never use vague phrases like "general inspection" or "entire property" - State boundaries of what entrant will and will not do ### Step 3: Build Entry Window - Match Agreement's format (specific time vs. range); always specify time zone - Primary + backup window only if Agreement permits - Confirm site-specific restrictions (noise ordinances, HOA rules, permit windows) ### Step 4: Identify Entrants and Equipment - Detail level per Agreement (named individuals vs. company + supervisor) - Omit unnecessary personal data unless Agreement requires it - Equipment descriptions must be honest and complete — under-disclosure appears deceptive - Reference restoration/safety provisions for heavy equipment or invasive activities ### Step 5: Confirm Insurance - COIs verified and in hand → state compliance and attach - COIs pending → state intention and timing; do NOT represent coverage as confirmed - Include policy types/limits only if verified from the certificate - **Never state "fully insured"** without confirming terms against Agreement requirements ### Step 6: Assemble the Notice Use this structure: [Date] [Recipient Name and Address per Notice Clause] Re: Notice of Entry — [Agreement Title] dated [Date] — [Property Address] Pursuant to Section [__] of the [Agreement Title] dated [Date] between [Entering Party] and [Owner] (the "Agreement"), this letter constitutes [lead time] advance written notice of Entering Party's intended entry onto the property located at [Address] (the "Property"). DATE AND TIME OF ENTRY. [Day, Date], arrival at approximately [time] [time zone], with anticipated completion by [time]. PURPOSE AND SCOPE. Entry will be for the limited purpose(s) authorized under Section [__] of the Agreement, specifically: [describe activities]. No activities outside the scope of the Agreement are intended. AREAS TO BE ACCESSED. Personnel will access only the following areas: [describe with exhibit references]. PERSONNEL AND CONTRACTORS. [List with roles and company affiliations]. The onsite supervisor will be [Name], reachable at [phone]. EQUIPMENT AND VEHICLES. [Describe]. [Vehicle information if required]. INSURANCE. Entering Party confirms compliance with the insurance requirements of Section [__] of the Agreement. [Certificate(s) attached as Exhibit [__] / previously provided on [date]]. Please advise promptly if the Property requires a specific check-in procedure, escort, or safety orientation. Absent written objection on a basis permitted by the Agreement, Entering Party intends to proceed as noticed. Sincerely, [Name / Title / Contact Information] cc: [All parties required by notice clause] Enclosures: [COIs; Site Plan if applicable] ### Step 7: Adversarial-Proof and Finalize - [ ] No unnecessary admissions (liability, causation, ownership of conditions) - [ ] No promises beyond contractual obligations - [ ] No privileged strategy, settlement positions, or sensitive information - [ ] Language tethered to Agreement terms throughout - [ ] Delivery via all methods required by Agreement; recommend redundant delivery for high-stakes entries ## Checkpoint B: Post-Draft Alignment After delivering the draft, ask: 1. Does the entry window comply with the notice period counting business days? 2. Are all activities within the Agreement's permitted scope? 3. Are COIs current and matching Agreement insurance requirements? 4. Is there a lender, property manager, or tenant who must receive a copy? If no response, recommend verifying the calendar calculation (most common failure) and proceed if authorized. ## Quality Audit | Check | Verify | |---|---| | **Calendar** | Receipt-to-entry interval meets/exceeds contractual requirement (business days, weekends, holidays) | | **Scope** | Every activity within Agreement's permitted activities | | **Recipient** | Addressee and delivery method match notice clause; all cc parties included | | **Insurance** | COI attached, limits match, correct additional insureds and endorsements | | **Contact** | Onsite point of contact provided | | **Facts** | Every assertion confirmed by user inputs or documentation | | **Tone** | Firm notice asserting rights — not requesting permission, not argumentative | | **Format** | Clear subject line, Agreement reference, consistent defined terms, clean signature block | ## Pitfalls and Checks **Jurisdiction notes:** | Jurisdiction | Consideration | |---|---| | California | Cal. Civ. Code § 1954: 24-hour statutory notice for residential landlord entry. Commercial access governed by contract. | | New York | RPAPL § 881 `[VERIFY]`: summary proceeding for license to enter adjoining property. | | Texas | Strict property rights; entries risking permanent land injury need clear remediation plans. | | Federal environmental | CERCLA entries (42 U.S.C. § 9604(e)) must cite statutory authority or docket number. | **Anti-hallucination rules:** - Never fabricate lead times, policy limits, scope permissions, or legal citations - Mark unverified statutes with `[VERIFY]` - Never invent Agreement terms or section numbers **Operational rules:** - Flag statutory overlays (environmental regs, asbestos/lead paint, tenant notice statutes) for regulated activities - If entry plan changes post-notice, determine whether Agreement requires revised/supplemental notice - Preserve full record: notice, delivery confirmations, attachments, responses
Related Skills
protest-notice
Drafts a formal Notice of Intent to Protest Award for federal contracts under FAR 33.103, 33.104, and 4 C.F.R. Part 21. Use when a client receives an adverse contract award decision and must preserve GAO protest rights within the 10-day jurisdictional deadline. Covers bid protests, stay of performance requests, and contracting officer notifications.
notice-to-perform
Drafts a U.S. residential real estate Notice to Perform (cure notice) identifying contractual defaults, demanding specific cure actions, and preserving remedies. Use when drafting a notice to perform, notice to cure, default notice, or breach-and-cure letter for a residential purchase agreement or lease.
notice-to-perform-real-estate
Drafts jurisdiction-aware residential real-estate notices to perform (cure demands) for lease, purchase, or construction agreements where a counterparty has defaulted. Trigger when the user needs a notice to perform, notice to cure, cure notice, demand to perform, residential default notice, or pre-suit notice for a U.S. residential real-estate matter.
notice-of-prior-art
Drafts a Notice of Prior Art disclosing references material to patentability under 35 U.S.C. §§ 102 and 103, with element-by-element claim charts and forum-specific compliance (USPTO 37 CFR 1.56, district court local patent rules, PTAB 35 U.S.C. § 311). Use when preparing invalidity contentions, duty-of-disclosure filings, inter partes review petitions, or pre-litigation prior art disclosures.
notice-of-assets-claims
Drafts a Notice of Assets and Request for Claims for probate estates. Triggers when administering an estate, publishing creditor notice, filing a probate notice of assets, or establishing claim bar dates. Handles jurisdictional research, asset disclosure, claim filing procedures, and execution requirements under state-specific probate codes.
notice-of-appearance
Drafts a Notice of Appearance of Counsel for federal or state court with caption formatting, bar admission verification, e-filing signatures, and certificate of service. Use when an attorney is entering, substituting, or joining as counsel of record in litigation.
notice-of-appeal
Drafts a Notice of Appeal to initiate appellate review of a trial court judgment or order in US federal and state courts. Use when filing a notice of appeal, commencing appellate review, or preserving appellate jurisdiction after an adverse ruling.
notice-of-appeal-criminal
Drafts Notices of Appeal for criminal matters with strict compliance to FRAP 4(b) deadlines, jurisdictional statements, transcript requests, and service requirements. Use when filing a criminal appeal, initiating appellate review after conviction or sentencing, or preparing post-trial appellate filings.
notice-of-annual-shareholders-meeting
Drafts a U.S. corporate annual shareholders meeting notice enforcing record-date accuracy, notice timing, quorum/vote thresholds, proxy logistics, and agenda disclosures under charter/bylaws and state statutes. Triggers on requests involving annual meeting notice, shareholder meeting notice, record date, quorum, proxy voting, or annual meeting agenda.
hipaa-privacy-notice
Drafts a HIPAA-compliant Notice of Privacy Practices per 45 CFR § 164.520 for covered entities. Produces patient-accessible documents covering permitted PHI uses/disclosures, individual rights, breach notification, and complaint procedures. Use when drafting HIPAA privacy notices, NPP documents, patient privacy disclosures, or covered entity privacy practice notices.
glba-privacy-notice
Drafts GLBA-compliant privacy notices using the 16 CFR Part 313 Appendix A model form safe harbor. Use when creating or updating Regulation P privacy notices, annual consumer disclosures, or NPI sharing notices for banks, credit unions, securities firms, insurers, or other covered entities under 15 U.S.C. §§ 6801–6809.
fairness-hearing-notice
Drafts FRCP 23(e)-compliant class action fairness hearing notices. Extracts settlement terms, class definition, deadlines, and court-mandated language from case documents to produce plain-language notices satisfying due process. Use when drafting settlement notices, fairness hearing notices, class action notice of proposed settlement, or CAFA notices.