Skills context-daddy

📦

context-daddy

Name: context-daddy
Author: ChipFlow

Content revision r3 Low Risk 🌐 Network access⚙️ External commands📁 Filesystem access🔑 Env variables

Map large codebases with focused symbol search

Large repositories can overwhelm code exploration and consume limited context. This skill builds a local symbol index so you can retrieve targeted code and preserve project knowledge.

Supports: Claude Codex Code(CC)

📊 76 Adequate

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "context-daddy" from https://skillstore.io/skills/chipflow-context-tools.md and its manifest at https://skillstore.io/api/skills/chipflow-context-tools/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/chipflow-context-tools.md Signed manifest GET /api/skills/chipflow-context-tools/manifest Signed lockfile GET /api/skills/chipflow-context-tools/lockfile

Test it

Using "context-daddy". Find the ConfigLoader class.

Expected outcome:

ConfigLoader found in src/config/loader.py.
The result includes its signature, source location, and available methods.

Using "context-daddy". What symbols are in src/utils.py?

Expected outcome:

A file-level list of functions and classes with signatures.
A concise summary of the module’s public responsibilities.

Using "context-daddy". Check repository indexing status.

Expected outcome:

Index status: completed.
The response reports symbol count and the most recent index time.

Security Audit

Low Risk

v11 • 7/18/2026 Open versioned report

All 94 static findings are false positives caused by documentation, metadata, and static assets. The reviewed material describes local indexing and optional tooling, with no evidence of credential exfiltration, malicious persistence, prompt injection, or executable command injection.

Files scanned

1,450

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Low

mermaid.min.js:1

Unscanned file (too_large) — manual review required

[unscanned: too_large]

Force-confirmed metadata/low static finding; AI false-positive verdict rejected.

Risk Factors

🌐 Network access (5)

book.toml:11 book.toml:12 logo2.svg:10 logo2.svg:11 mermaid-init.js:3

⚙️ External commands (50)

📁 Filesystem access (12)

CHANGELOG.md:49 CHANGELOG.md:109 CHANGELOG.md:49 CHANGELOG.md:109 CLAUDE.md:76 CLAUDE.md:118 CLAUDE.md:76 CLAUDE.md:118 README.md:95 README.md:138 README.md:95 README.md:138

🔑 Env variables (2)

CLAUDE.md:140 README.md:145

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/chipflow-context-tools/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/chipflow-context-tools/security.svg)](https://skillstore.io/skills/chipflow-context-tools?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/chipflow-context-tools?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chipflow-context-tools/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/chipflow-context-tools.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

ChipFlow. (2026). context-daddy security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chipflow-context-tools/audits/11

BibTeX citation

@techreport{chipflow-chipflow-context-tools-2026,
  author = {ChipFlow},
  title = {context-daddy security audit report (audit version 11)},
  institution = {Skillstore},
  year = {2026},
  number = {11},
  url = {https://skillstore.io/skills/chipflow-context-tools/audits/11},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "context-daddy security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
  - name: "ChipFlow"
date-released: "2026-07-18"
url: "https://skillstore.io/skills/chipflow-context-tools/audits/11"
identifiers:
  - type: other
    value: "skillstore:chipflow-context-tools:audit:11"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Navigate an unfamiliar service

Find the relevant classes and functions before changing a large existing codebase.

Prepare an implementation plan

Locate related symbols and dependencies to create a focused technical plan.

Preserve team knowledge

Maintain project narratives, learnings, and goals across Claude Code sessions.

Try These Prompts

Find a symbol

Find the symbol named AuthService and show its signature, location, and related methods.

Explore a module

List the indexed symbols in src/api.py. Summarize each public function in one sentence.

Trace an implementation

Search for symbols related to payment retries. Identify the main flow and the files I should review.

Plan a safe change

Use the repository map to find all symbols affected by adding a cache to the config loader. Propose a change plan and test scope.

Best Practices

Use symbol search before broad text search when you know a code identifier.
Wait for initial indexing to complete before relying on symbol results.
Review generated narratives and learnings before treating them as team documentation.

Avoid

Do not use the index as the only source of truth for unindexed languages or generated files.
Do not store secrets in project narratives, learnings, or goals.
Do not assume a symbol search result proves runtime behavior without reviewing the source.