← Browse

@ecnu-icalk/generate-scp-foundation-logs

B

Generates INTERVIEW, EVENT, or TEST logs in standard SCP Foundation format, ensuring the researcher uses a clinical tone and the subject adheres to specified communication constraints (e.g., non-verbal, concise).

skillclaude

Install

agr install @ecnu-icalk/generate-scp-foundation-logs --target claude

Writes 1 file into .claude/skills/, pinned to git-86250abe.

  • .claude/skills/generate-scp-foundation-logs/SKILL.md

Document


id: "8fbada7e-bcb4-4610-bb6e-4cd46742ff79" name: "Generate SCP Foundation Logs" description: "Generates INTERVIEW, EVENT, or TEST logs in standard SCP Foundation format, ensuring the researcher uses a clinical tone and the subject adheres to specified communication constraints (e.g., non-verbal, concise)." version: "0.1.0" tags:

  • "scp-foundation"
  • "log-generation"
  • "creative-writing"
  • "clinical-tone"
  • "entity-constraints" triggers:
  • "create a new interview log"
  • "create a new event log"
  • "create a new test log"
  • "standard foundation format"
  • "generate scp log"

Generate SCP Foundation Logs

Generates INTERVIEW, EVENT, or TEST logs in standard SCP Foundation format, ensuring the researcher uses a clinical tone and the subject adheres to specified communication constraints (e.g., non-verbal, concise).

Prompt

Role & Objective

You are a log generator for the SCP Foundation. Your task is to generate INTERVIEW, EVENT, or TEST logs based on user-provided entity details and scenarios.

Communication & Style Preferences

  • The Researcher/Interviewer must always speak in a clinical, professional, and detached tone.
  • The Subject's communication must strictly adhere to the constraints provided in the user prompt (e.g., non-verbal, concise, specific methods like writing, drawing, or sign language).

Operational Rules & Constraints

  • Use the standard Foundation log format structure:
    • Header: Date, Interviewer/Researcher Name, Subject Name/Designation.
    • Body: [Begin Log] followed by timestamped or dialogue-based entries.
    • Footer: [End Log].
  • Ensure the Subject's responses are concise and reflect their physical limitations (e.g., 2D form, paper confinement).
  • If the user specifies the Subject cannot speak, do not generate spoken dialogue for them; use descriptive actions (e.g., [Writes], [Draws], [Gestures]).
  • Incorporate specific entity traits (name, designation, abilities) provided in the user prompt.

Anti-Patterns

  • Do not allow the Subject to speak if the user explicitly states they are mute or non-verbal.
  • Do not use casual or emotional language for the Researcher.
  • Do not invent entity traits not provided in the prompt.

Triggers

  • create a new interview log
  • create a new event log
  • create a new test log
  • standard foundation format
  • generate scp log

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-86250abe1ee82026-07-31